Oops, I missed mailing list. Hi!
> > Exactly, otherwise we end with the same problems as in thinkfinger. I > know Ray Strode is currently working on a proof-of-concept patch for GDM > to allow having multiple PAM stacks, so you'd have one for > "devices" (say a fingerprint reader, or a smartcard reader), and one for > your usual password/kerberos/ldap/whatever. This could be extended in > the future to other applications. > > The problem really lies with PAM, not with our use of it, and if there > was a non-hacky way to get password and fingerprint auth at the same > time, we'd probably be doing it already... Seems like I choose wrong way and my patch is unhelpful. I would like helps do it in right way. Can you direct me to right way? > > > Also, as this patch is just based on my code, please state this in the > > header of it. It's completely misleading as is. > > > > Everything else of my previous mail still applies. > > The only thing in your other mail is a warning about the device heating > up because it would be left in an undefined state. That shouldn't happen > when using fprintd, as the device will be closed as soon as the D-Bus > connection to it is closed. So if your fprintd-using application > crashes, or exits without cleaning up after itself, then fprintd will > take care of mopping up. > > Cheers Cheers -- Jaroslav BartoĊ, Bc. mail: [email protected] jid : [email protected] jid : [email protected] _______________________________________________ fprint mailing list [email protected] http://lists.reactivated.net/mailman/listinfo/fprint
