-
-
Notifications
You must be signed in to change notification settings - Fork 44
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
Block fprint unlock on gdm #163
Comments
I'm confused by this cause it seems like multiple issues in one 😄 On the one hand, you're asking for fprint unlock to be blocked for some reason (why?). On the other hand, you're reporting a bug. Can you please clarify the core goal for this issue? |
so, I was
I think the default timeout is 2 failed tries at least in the terminal for sudo. This may be different on gdm (and in the future sddm) and also different in plasma and gnome screenlocker. |
for 1, I'm confused. if it already locks after a few failures, that seems like desired behavior. potentially #127 is related for 2, please check upstream silverblue-main like you mentioned and if you can't repro there, reopen this issue. Otherwise this is likely an issue with the package itself and you can report it to the maintainers. |
Yes this is a PAM issue. The relevant PAM service stacks are unchanged from Fedora. This hsould be tested on a normal Silverblue VM. |
SDDM doesnt, but GDM supports login with fingerprint.
SDDM may support this soon too, it was planned for Plasma 6.
A better option would be something like GrapheneOS, which afaik locks the fingerprint after 3 failed attempts.
On my hardware this is nearly always the case though, because that sensor sucks. It will be more secure though.
Also, fprint-enroll is broken somehow on Silverblue-main-hardened, but I havent tried regular silverblue-main. It works perfectly fine in the TUI, which smells like an upstream bug.
The text was updated successfully, but these errors were encountered: