https://bugs.kde.org/show_bug.cgi?id=453877
--- Comment #4 from Éric Brunet <eric.bru...@lps.ens.fr> ---
I agree it should be PAM's job, but they don't seem to think so. From the
manpage for pam_fprintd:
The PAM stack is by design a serialised authentication, so it is not
possible for pam_fprintd to allow authentication through passwords and
fingerprints at the same time.
It is up to the application using the PAM services to implement
separate PAM processes and run separate authentication stacks
separately. This is the way multiple authentication methods are made
available to users of gdm for example.
So maybe it is up to kscreenlocker to do the work, after all. There must be
some code in gdm that could be adapted in kscreenlocker and in sddm.
--
You are receiving this mail because:
You are watching all bug changes.
