Ubuntu
fgetty package

checkpassword apparently broken in Jaunty

Bug #372025 reported by arboc
30
This bug affects 4 people
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).

Revision history for this message
arboc (dcobra) wrote :

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)

Revision history for this message
arboc (dcobra) wrote :

Please ignore my guess about PAM. It seems fgetty doesn't use it at all. It must be something else.

Revision history for this message
pothos (pothos) wrote :

Could anything be done to fix the failing checkpassword?
For me fgetty is unusable…
fgetty-longin2 brings up a "Segmentation fault"
fgetty-login says every time "wrong password" while I press enter; so I think, it crashes, because normally it should wait a few seconds when a wrong password is entered.
Is there anyone with a healthy fgetty?
Greetings,
Kai

Revision history for this message
pothos (pothos) wrote :

I know no running fgetty & checkpassword in ubuntu, but the bug is not mentioned.

Revision history for this message
Chris Stork (cstork) wrote :

Here's an strace. HTH.

root:~# printf "%s\0%s\0%s\0" bob s3cr3t Y2009 | strace checkpassword true 3<&0
execve("/bin/checkpassword", ["checkpassword", "true"], [/* 21 vars */]) = 0
open("/dev/urandom", O_RDONLY) = 4
read(4, "\256\17\273\37\16\272d\267"..., 8) = 8
close(4) = 0
arch_prctl(ARCH_SET_FS, 0x603020) = 0
read(3, "bob\0s3cr3t\0Y2009\0"..., 512) = 19
read(3, ""..., 493) = 0
close(3) = 0
open("/etc/passwd", O_RDONLY) = 3
lseek(3, 0, SEEK_END) = 1935
mmap(NULL, 1935, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f0dcbb67000
close(3) = 0
munmap(0x7f0dcbb67000, 1935) = 0
open("/etc/shadow", O_RDONLY) = 3
lseek(3, 0, SEEK_END) = 1417
mmap(NULL, 1417, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f0dcbb67000
close(3) = 0
munmap(0x7f0dcbb67000, 1417) = 0
ioctl(0, SNDCTL_TMR_TIMEBASE or TCGETS, 0x7fffd3b67030) = -1 EINVAL (Invalid argument)
_exit(1) = ?

Revision history for this message
tai (tai-launchpad) wrote :

Could this be related?

- http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563335
> Fgetty doesn't support the sha512 algorithm that is used as default in debian squeeze for shadow passwords.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.