FS#61730 - [kbd][pambase] vlock broken by recent pambase update
Attached to Project:
Arch Linux
Opened by Michael Gwin (oksijun) - Tuesday, 12 February 2019, 09:54 GMT
Last edited by Tobias Powalowski (tpowa) - Friday, 14 August 2020, 12:27 GMT
Opened by Michael Gwin (oksijun) - Tuesday, 12 February 2019, 09:54 GMT
Last edited by Tobias Powalowski (tpowa) - Friday, 14 August 2020, 12:27 GMT
|
Details
Description:
Since the pambase update from 20171006-1 to 20190105.1-1, the restrictive defaults in /etc/pam.d/other have broken vlock, which no longer accepts input and fails with the following error: "pam_warn(vlock:auth): function=[pam_sm_authenticate] flags=0 service=[vlock] terminal=[tty2] user=[<redacted>] ruser=[<unknown>] rhost=[<unknown>]" Creating /etc/pam.d/vlock with the following contents (the previous contents of /etc/pam.d/other) resolves the issue: #%PAM-1.0 auth required pam_unix.so account required pam_unix.so password required pam_unix.so session required pam_unix.so Additional info: * package version(s): 2.0.4-2 Steps to reproduce: Lock the terminal (e.g. by running "vlock -a" |
This task depends upon
Closed by Tobias Powalowski (tpowa)
Friday, 14 August 2020, 12:27 GMT
Reason for closing: Fixed
Additional comments about closing: 2.3.0-2
Friday, 14 August 2020, 12:27 GMT
Reason for closing: Fixed
Additional comments about closing: 2.3.0-2
The entire console display is now completely locked by tangxinfa.
Authentication failure.
Be carefull to test it by add a timeout
timeout -s KILL 10 vlock -a