You are not logged in.
So I have already setup libfprint/pam_fprint for my login screen and now i want to set it up so I can use my fingerprint reader for the "Enter the administrative password" dialog when you try to access stuff like "Login Window". What file do I have to edit to do this?
Thank you
Last edited by FLCLFan (2008-07-27 22:24:06)
Offline
I found the program its gksu. I added a line to /etc/pam.d/su "auth sufficient pam_fprint.so". But when i try to use it I get "Could not locate any suitable fingerprints match with available hardware". Anyone know how to fix this?
Offline
If your using KDE 4.1, you can ask kdesu to use sudo:
kwriteconfig -file kdesurc -group super-user-command -key super-user-command sudo
In my /etc/pam.d/kde file I have:
auth sufficient pam_fprint.so
Then call kdesu to open your stuff:
kdesu kate
Unfortunately, kdesu wont show you a window saying "Please swipe finger..." but I just know it is waiting, so I wipe the finger and the window opens.
Offline
Im using gnome on my computer so how would i make it work with that? The only things i have done are:
Installed libfprint, pam_fprint, and fprint_demo (have to use sudo to access), then setup 2 fingers.
Then I edited:
/etc/pam.d/gdm
#%PAM-1.0
auth requisite pam_nologin.so
auth required pam_env.so
auth sufficient pam_fprint.so
auth sufficient pam_unix.so try_first_pass likeauth nullok
auth required pam_deny.so
#auth required pam_unix.so
account required pam_unix.so
session required pam_limits.so
session required pam_unix.so
password required pam_unix.so
(GDM login works fine)
/etc/pam.d/su
#%PAM-1.0
auth sufficient pam_rootok.so
auth sufficient pam_fprint.so
# Uncomment the following line to implicitly trust users in the "wheel" group.
#auth sufficient pam_wheel.so trust use_uid
# Uncomment the following line to require a user to be in the "wheel" group.
#auth required pam_wheel.so use_uid
auth required pam_unix.so
account required pam_unix.so
session required pam_unix.so
Which gives "Could not locate any suitable fingerprints match with available hardware" in gksu and it does not light up my reader.
Offline
Hum...
I would put the rule as the first one. But its probably not the cause of the problem.
After some googling, I think it might be because you set up the reader under root, but trying to access it with normal user...
Copy /root/.fprint to ~/ and then change ownership.
Offline
Okay, i did that, i can access the setting stuff without sudo. But it didnt fix the problem.
But what i did find out is that when I do "$ su eli" in terminal it works and asks for my fingerprint. Its something with gksu.......
Offline
Maybe you need a gksu file in /etc/pam.d ?
Offline
That does nothing.
Offline
So does anyone think there is a way to integrate fprint into gksu?
Offline
Yes there is, I think I already used it. But then I'm out of ideas on why it doesn't work for you... :S
Offline