vlock version 1.3 doesn't work at all. When run, it uses 100% of the cpu and repeatedly prints the following messages to the screen. It does this in a terminal in X and also on the console. It any input is given in the terminal vlock ignores it untill it is killed, and then outputs whatever was typed to the console. If you attempted to type in your password, then your password is output in plain text to the console. This was duplicated on 2 different machines, both running gentoo 1.1a. liverbugg@alumiguin liverbugg $ vlock This TTY is now locked. Please enter the password to unlock. liverbugg's root's *** That password is incorrect; please try again. *** This TTY is now locked. Please enter the password to unlock. liverbugg's root's *** That password is incorrect; please try again. *** This TTY is now locked. Please enter the password to unlock. liverbugg's root's *** That password is incorrect; please try again. *** This TTY is now locked. Please enter the password to unlock. liverbugg's root's *** That password is incorrect; please try again. ***
I found a solution, see bug 2073. the same thing is wrong with vlock. There is no entry in /etc/pam.d for vlock. Make a file called vlock in /etc/pam.d and put the following in it. #%PAM-1.0 auth required /lib/security/pam_stack.so service=system-auth Either vlock or pam should provide these files to prevent this from happening in the future and for other packages.
Sorry, I should have said the same thing is wrong with xlock, not the same thing is wrong vlock.
Should be all set now in vlock-1.3-r1. Thanks for the bug report (and resolution).
