sudo segmentation fault when using pam_fprint
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
sudo (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: sudo
Ubuntu Hardy 8.04.1 (2.6.24-19-generic #1 SMP Fri Jul 11 21:01:46 UTC 2008 x86_64 GNU/Linux)
Current version of Sudo: 1.6.9p10-1ubuntu3.2
This bug was discovered with the use of pam_fprint (fingerprint authentication module, see http://
After installing pam_fprint and testing and enlisting fingers via fprint_demo, I edited /etc/pam.
# this enables the fingerprint reader
auth sufficient pam_fprint.so
# original:
# auth requisite pam_unix.so nullok_secure
# modifed so fingerprint reader is sufficient without password
auth sufficient pam_unix.so nullok_secure
At first use, it works fine (*What happened*):
$ sudo nano /etc/pam.
Scan right little finger on AuthenTec AES2501
Then, the second time, the bug appears:
$ sudo nano /etc/pam.
Segmentation fault
$
Note that if using standard password authentication, you will not be asked for password at this time as the sudo session has not timed out yet. When the sudo session has timed out, or if I use "sudo -k" to induce timeout, it works fine again - the first time - as demonstrated above.
According to the Debian bug report mentioned above, the bug is fixed in version: 1.6.9p15
I installed the latest version found here: http://
Sudo version is now: 1.6.9p17-1
It now works as expected (*What I expected to happen in the first place*):
$ sudo nano /etc/pam.
Scan right little finger on AuthenTec AES2501
$ sudo nano /etc/pam.
Scan right little finger on AuthenTec AES2501
$
My request here is merely for this later version of sudo to be included in hardy-updates or the backports repositories of Ubuntu.
description: | updated |
description: | updated |
description: | updated |
I can just confirm this, wouldn't have solved it as fast without this bugreport - thanks!