Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fingerprint reader support #20

Open
soumendu041 opened this issue Jun 28, 2018 · 8 comments
Open

Fingerprint reader support #20

soumendu041 opened this issue Jun 28, 2018 · 8 comments

Comments

@soumendu041
Copy link

Thanks for making this very polished theme. Currently, there is no prompt such as "swipe your fingerprint to login" like the stock antergos theme for webkit2-greeter. One has to press enter while in the password entry box to activate the fingerprint reader. Also, if fingerprint authentication fails, it does not fall back to the usual password authentication. I'm on Arch.

@Litarvan Litarvan mentioned this issue Jul 14, 2018
Merged
@Litarvan
Copy link
Owner

I dont really understand what i'm supposed to do, "One has to press enter while in the password entry box to activate the fingerprint reader" ? I mean, i don't think there is an API in webkit2-greeter for it, is there? Thought fingerprint devices just typed password themselves, i'll try to figure how it works, but can you explain more in details what you do on the regular antergos theme, and what you are doing to make it work on my theme ?

@WingofaGriffin
Copy link

WingofaGriffin commented Jan 28, 2019

I feel like this has something to do with PAM, but I'm not entirely sure what the issue would be. Trying to configure howdy to work with lightdm (with light-locker as the screensaver) currently is not working as intended, making me put in the password, then my face instead of just allowing one or the other.

It's unclear if this is a limitation of lightdm, webkit2 greeter, or this theme to me, and I think the fingerprint is an error in the same manner.

Edit: This issue is probably the same thing.

@FFY00
Copy link

FFY00 commented Jan 28, 2019

@WingofaGriffin it's not. #33 refers to HTOP which is an One time password algorithm, which mean you have a generator app/device that generates a different password each time you login. It's similar to standard time based 2FA (which is actually TOTP) but instead of the password changing based on the current time, it changes every time a password used.

Next month I am going to get a new laptop and it happens to have a fingerprint reader. Perhaps I can do some digging then and help with the resolution of this problem.

@WingofaGriffin
Copy link

Ah that's a shame. I'd do some testing myself if my fingerprint reader was supported (damn Synaptics!)

@scrouthtv
Copy link

I don't know if someone still cares about this, but the issue is still open, so:

The fingerprint login worked for me by adding

auth      sufficient pam_fprintd.so

to /etc/pam.d/system-local-login (see https://wiki.archlinux.org/index.php/Fprint#Configuration).

@bjornsnoen
Copy link

@scrouthtv does it still work for you with only that line added? What does it look like? For me it does not have any effect on the greeter, I only have password login available.

@scrouthtv
Copy link

@bjornsnoen webkit greeter is currently broken for me, so I can't tell

@rt-kill
Copy link

rt-kill commented Nov 1, 2022

As instructed by Archwiki, I had the following lines in /etc/pam.d/system-local-login,

auth sufficient pam_fprintd_grosshack.so
auth sufficient pam_unix.so try_first_pass nullok
auth sufficient pam_fprintd.so

I was unable to log in using this theme -- I needed to boot into runlevel 3, and change the greeter back to slick-greeter (which works well with fprint).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants