-
Notifications
You must be signed in to change notification settings - Fork 98
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
PAM setup including pam_fprintd #356
Comments
My guess would be it's an ordering issue in your various pam configuration files. You can turn on debugging for There are two things
We would need to know which piece of functionality wasn't working. |
here's the content of all PAM files that contain either pam_fscrypt or pam_fprintd, and SDDM:
this is what i get in my syslog with the above configuration when attempting to login via SDDM (password):
trying login on a console:
login after deactivating pam_fprintd:
|
i've sucessfully set up encrypted home using pam_fscrypt. after that, i configured a fingerprint sensor for login (SDDM/console). that also worked pretty well, but when i rebooted i noticed that while i was able to log in using a fingerprint, my home was no longer decrypted, hence KDE won't start (SDDM hangs). i suspected this was due to the fact that obviously i didn't provide a password, so the protector can't be unlocked.
however, this issue remained even when i logged in with a password instead of a figerprint, and only went away after i completely deactivated pam_fprintd again. configuration was done using
pam-auth-update
on kubuntu 22.04 (fscrypt v0.3.3).is there a proper way of cofiguring pam_fscrypt together with pam_fprintd?
The text was updated successfully, but these errors were encountered: