Public bug reported:

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://reactivated.net/fprint/wiki/Pam_fprint) in 
/etc/pam.d/common-auth, but a similar issue 
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=462445) which does not 
include the same module was solved in Debian's unstable branch so I gave the 
solution a try and it worked.
After installing pam_fprint and testing and enlisting fingers via fprint_demo, 
I edited /etc/pam.d/common-auth to include the following:
# 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.d/common-auth
Scan right little finger on AuthenTec AES2501

Then, the second time, the bug appears:
$ sudo nano /etc/pam.d/common-auth
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://packages.debian.org/sid/amd64/sudo/download
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.d/common-auth
Scan right little finger on AuthenTec AES2501

$ sudo nano /etc/pam.d/common-auth
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.

** Affects: sudo (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: fault fprint pam segfault segmentation sudo

** Description changed:

  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://reactivated.net/fprint/wiki/Pam_fprint) in 
/etc/pam.d/common-auth, but a similar issue 
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=462445) which does not 
include the same module was solved in Debian's unstable branch so I gave the 
solution a try and it worked.
  After installing pam_fprint and testing and enlisting fingers via 
fprint_demo, I edited /etc/pam.d/common-auth to include the following:
+ # 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
+ 
  
  What happened:
  
  At first use, it works fine:
  $ sudo nano /etc/pam.d/common-auth
  Scan right little finger on AuthenTec AES2501
  
  Then, the second time, the bug appears:
  $ sudo nano /etc/pam.d/common-auth
  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://packages.debian.org/sid/amd64/sudo/download
  Sudo version is now: 1.6.9p17-1
  
  What I expected to happen:
  
  It now works as expected:
  $ sudo nano /etc/pam.d/common-auth
  Scan right little finger on AuthenTec AES2501
  
  $ sudo nano /etc/pam.d/common-auth
  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 changed:

  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://reactivated.net/fprint/wiki/Pam_fprint) in 
/etc/pam.d/common-auth, but a similar issue 
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=462445) which does not 
include the same module was solved in Debian's unstable branch so I gave the 
solution a try and it worked.
  After installing pam_fprint and testing and enlisting fingers via 
fprint_demo, I edited /etc/pam.d/common-auth to include the following:
  # 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
  
- 
- What happened:
- 
- At first use, it works fine:
+ At first use, it works fine (*What happened*):
  $ sudo nano /etc/pam.d/common-auth
  Scan right little finger on AuthenTec AES2501
  
  Then, the second time, the bug appears:
  $ sudo nano /etc/pam.d/common-auth
  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://packages.debian.org/sid/amd64/sudo/download
  Sudo version is now: 1.6.9p17-1
  
- What I expected to happen:
- 
- It now works as expected:
+ It now works as expected (*What I expected to happen in the first place*):
  $ sudo nano /etc/pam.d/common-auth
  Scan right little finger on AuthenTec AES2501
  
  $ sudo nano /etc/pam.d/common-auth
  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 changed:

  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://reactivated.net/fprint/wiki/Pam_fprint) in 
/etc/pam.d/common-auth, but a similar issue 
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=462445) which does not 
include the same module was solved in Debian's unstable branch so I gave the 
solution a try and it worked.
  After installing pam_fprint and testing and enlisting fingers via 
fprint_demo, I edited /etc/pam.d/common-auth to include the following:
  # 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.d/common-auth
  Scan right little finger on AuthenTec AES2501
  
  Then, the second time, the bug appears:
  $ sudo nano /etc/pam.d/common-auth
  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.
+ 
+ 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://packages.debian.org/sid/amd64/sudo/download
  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.d/common-auth
  Scan right little finger on AuthenTec AES2501
  
  $ sudo nano /etc/pam.d/common-auth
  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.
+ 
+ My request here is merely for this later version of sudo to be included in 
hardy-updates or the backports repositories of Ubuntu.

-- 
sudo segmentation fault when using pam_fprint
https://bugs.launchpad.net/bugs/254599
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to