checkpassword apparently broken in Jaunty
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
fgetty (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: fgetty
I am attempting to use runit in place of upstart to manage tty1 through tty6, due to runit's better handling of utmp (upstart leaves stale utmp entries after one logs out, confusing "finger", "last", etc. - see bug # 183729). Using runit worked fine in Hardy and Intrepid, but in Jaunty trying to login at one of the ttys fails with "checkpassword: wrong password". Upstart uses getty, while runit uses fgetty. Apparently, something broke in the fgetty package between Hardy and Jaunty, causing failure of the password check.
(Note that I did not install runit-run, only runit, which is enough to fix the problem in utmp, without actually abandoning the /sbin/init scheme).
Steps to reproduce:
1. From any terminal, run /bin/fgetty-login
2. Enter login name and password
3. Login fails with "checkpassword: wrong password"
Running "sudo fgetty-login" fails equally.
Could this be a problem with PAM, due to fgetty's login and login2 being renamed fgetty-login and fgetty-login2 in Debian? (see /usr/share/ doc/fgetty/ README. Debian)