Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#61730 - [kbd] 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 Eli Schwartz (eschwartz) - Wednesday, 13 February 2019, 22:54 GMT
Task Type Bug Report
Category Packages: Extra
Status Assigned
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 8
Private No



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:

auth required
account required
password required
session required

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

Comment by tangxinfa (tangxinfa) - Wednesday, 13 February 2019, 06:37 GMT
This problem will lock your computer with the following countless messages

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
Comment by Maxim (mxfm) - Saturday, 07 September 2019, 16:51 GMT
Please fix (it is trivial to fix).
Comment by Ad Gaud (adgaud) - Sunday, 10 May 2020, 13:25 GMT
Seconded, please fix. Without vlock -a no quick means to lock all TTYs and leave the machine secure while unattended.