Maximilian Seidler
Maximilian Seidler
Sadly fingerprint won't work with greetd. Maybe as an additional factor, or maybe with some hack, but generally the greetd server itself must decide on if we have authenticated successfully...
That has absolutely nothing to do with this PR and also no, even if you use `systemd-homed`, allowing fprint to be the only factor is not sufficiently secure. Idk about...
Update on the PR: Rebased and we now have click support for the session-picker and I think I fixed the crash @VirtCode mentioned. Testing is welcome :)
So I am currently working on porting hyprlock to hyprtoolkit. But I still really want this feature to be part of hyprlock. I personally still use it in the current...
0.5.0 introduced fingerprint support outside of pam, since that does not work well in a lot of cases. This comment might help you: https://github.com/hyprwm/hyprlock/issues/258#issuecomment-2428006590
nevermind. because the formatting is broken i did not bother to check your config and see that you are already using the new fingerprint support. Can you post hyprlock logs...
it is literally on the readme... https://github.com/uunicorn/python-validity?tab=readme-ov-file#fingerprint-not-working-after-waking-up-from-suspend
does #544 change anything?
this really sounds like a open-fprintd problem
I think pam is fundamentally broken, so I am not entirely opposed to a custom Auth method. Two security relevant things. - hashing is too fast. we need an artificial...