auth sufficient means that device isn't required for authentication.
Have you tried auth required?
** Changed in: lightdm (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
Hi Marc,
in the situation described in comment #2, I can login with *un*plugged
device and *no* password like auto-login. I will try auth required
anyway.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
auth sufficient case
/etc/pam.d/common-auth:
authsufficient pam_usb.so
auth[success=1 default=ignore] pam_unix.so nullok_secure try_first_pass
authrequisite pam_deny.so
authrequiredpam_permit.so
authoptional
auth required case
/etc/pam.d/common-auth:
auth required pam_usb.so
auth [success=1 default=ignore] pam_unix.so nullok_secure try_first_pass
auth requisite pam_deny.so
auth required pam_permit.so
auth optional pam_ecryptfs.so unwrap
auth optional pam_cap.so
Tom: knows his password and has the
Ah, yes, I see what's happening now. The pam_usb module is granting
access without a prompt as soon as lightdm spawns which lightdm caches
even when you remove the token.
** Changed in: lightdm (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a
You can work around the behaviour by putting the following in the lightdm.conf
file:
greeter-hide-users=true
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1159457
Title:
lightdm
== logout==
Mar 25 00:58:29 test-machine lightdm[5833]: pam_unix(lightdm:session): session
closed for user usb-auth
== start ligthdm ==
Mar 25 00:58:31 test-machine lightdm: pam_unix(lightdm:session): session opened
for user lightdm by (uid=0)
Mar 25 00:58:31 test-machine lightdm:
7 matches
Mail list logo
