[arch-general] Unlocking the screen through fprintd
Hi all, I have been trying to get fprint working properly with screen lockers for months and have yet to find a working solution. I am using i3wm without DM. Login on the TTY and sudo work properly: They ask me to swipe the finger and then ask for my password if that didn't work. However, every screen locker I have tried that supports PAM at all (i3lock, xlockmore, xscreensaver, kscreenlocker) all ask for my fingerprint AFTER I typed in my password. Is there no way to make them check for my fingerprint first, and then for my password? Does anyone here do something similar? Cheers, Bennett -- GPG fingerprint: 871F 1047 7DB3 DDED 5FC4 47B2 26C7 E577 EF96 7808
On Thu, 20 Oct 2016 10:13:59 +0200, Bennett Piater wrote:
However, every screen locker I have tried that supports PAM at all (i3lock, xlockmore, xscreensaver, kscreenlocker) all ask for my fingerprint AFTER I typed in my password.
Unfortunately I can't help you, I'm just curious. If you type no password at all, just push enter, does the fingerprint check allow you to unlock the screen? Or doesn't it appear, if you just push enter without typing a password? Regards, Ralf
Unfortunately I can't help you, I'm just curious.
Well, you did anyway!
If you type no password at all, just push enter, does the fingerprint check allow you to unlock the screen? Or doesn't it appear, if you just push enter without typing a password?
I tested it with kscreenlocker and xlockmore and it works perfectly. Thanks a lot, I finally have a working setup now :) Curiosity didn't kill the cat, keep nurturing it ;) Cheers, Bennett -- GPG fingerprint: 871F 1047 7DB3 DDED 5FC4 47B2 26C7 E577 EF96 7808
Am 20.10.2016 um 10:13 schrieb Bennett Piater:
However, every screen locker I have tried that supports PAM at all (i3lock, xlockmore, xscreensaver, kscreenlocker) all ask for my fingerprint AFTER I typed in my password.
Not using fprint, but merely an idea (you have possibly already checked that): maybe the PAM-file for the screenlocker has a higher priority for passwords than for the fingerprint sensor while the rest has it the other way around. iirc this depends on the ordering of the corresponding modules in the respective PAM-files. ~ Jonas
Not using fprint, but merely an idea (you have possibly already checked that): maybe the PAM-file for the screenlocker has a higher priority for passwords than for the fingerprint sensor while the rest has it the other way around.
iirc this depends on the ordering of the corresponding modules in the respective PAM-files.
Thanks for chiming in! I had already checked that, in fact I wrote the PAM-files for the screen lockers myself. It doesn't matter though, since pressing enter without typing a password works, as I said in my reply to Ralf. I'll be doing that from now on :) Cheers, Bennett -- GPG fingerprint: 871F 1047 7DB3 DDED 5FC4 47B2 26C7 E577 EF96 7808
participants (3)
-
Bennett Piater
-
Jonas Große Sundrup
-
Ralf Mardorf