feat: handle PAM password policy changes
This commit is contained in:
@@ -12,10 +12,11 @@ Latchd has two test layers:
|
||||
|
||||
The Docker test image runs the first layer and starts an isolated Xvfb server
|
||||
when available. It does not use host display sockets, host PAM files, or a
|
||||
host VT. PAM authentication and a real login handoff require a disposable VM
|
||||
with a dedicated test account and an explicitly provisioned PAM policy; the
|
||||
container probe intentionally reports those checks as capability information
|
||||
only.
|
||||
host VT. The password-change path is covered by FFI/conversation tests in the
|
||||
container, but a real PAM password rotation and login handoff require a
|
||||
disposable VM with a dedicated test account and an explicitly provisioned PAM
|
||||
policy. The container probe intentionally reports those checks as capability
|
||||
information only.
|
||||
|
||||
For a local release-style run:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user