But tfm-fingerprint is masked in favor of thinkfinger, see bug #162297 Reproducible: Always
you dont need pam_bioapi either ... thinkfinger provides the pam module
then should pam_bioapi be masked also? so people moving over from tfm-fingerprint,will see it in the masking comment.
Why was tfm-fingerprint masked in the first place? I'm eager to switch to it, but currently it can't do all the stuff, that can be done with pam_bioapi. E.g. store multiple fingers, can't be used with KDM and can't carry a password which will be passed on to later pam-modules in the stack. The pam_bioapi in portage is also outdated btw. The current 0.4.0 version is available at: http://pam-bioapi.googlecode.com
Created attachment 130587 [details] pam_bioapi-0.4.0 ebuild This is an ebuild for the current pam_bioapi 0.4.0 which provides usage of multiple fingers and a password as payload, that will be passed to later modules in the pam-stack, e.g. to decrypt SSH-keys or such
(In reply to comment #3) > Why was tfm-fingerprint masked in the first place? > > I'm eager to switch to it Switch to ThinkFinger that is..
pam_bioapi-0.4.0 now in the tree