On Monday 25 February 2008 12:06:23 you wrote: > I know, that's fine. Imagine a daemon that you can ask for > identification of the finger. Anytime you may need a fingerprint, you > just connect to it. Then it can enable the fingerprint identification > procedure if it is not enabled yet. If your program decides that it does > not need the fingerprint anymore, it can disconnect. Otherwise it waits > for the daemon to provide the answer. What will be difficult to > implement here? The only hacking I see could be useful is splitting the > scanning and identification/authentication procedure, so you can decide > what to do with the fingerprint just after you got it.
Ok, agreed, so all we need is to design and implement this daemon. I think it's quite good solution. I've heard that Daniel works on somethink like that, so I think we should continue our discussion in maillist. > > so I think > > libfprint tweaking needed. The only problem we have - we can't determine > > when fingerprint from scanner is available. If we'll have such > > functionality from libfprint - we will not have that problem ;) > > I think our problems are also caused by the blocking nature of the > operations, right? But as far as I know this is connected to libusb. I don't know what causes problem, I didn't dig into :( > > Btw, all solutions that you've suggest are applicable for pam_fprint. The > > only trouble is to determine whether pam configured to use pam_fprint or > > not. Btw, what you will do if pam configured to use pam_fprint and kdm > > will use libfprint directly? > > You may need a separate configuration for kdm, agreed. But this would > allow logging in with either a fingerprint or a password. With > pam_fprint I just cannot see a configuration where you could log it with > either of the techniques in a natural way. Either a password or a > fingerprint has to be asked first. What if the user wants to log in > using another method? Ok, agreed, it will be more convenient to use kdm with authentification\identification daemon, but not with pam module directly. Regards Vasily P.S. Don't forget to add [email protected] in CC ;) _______________________________________________ fprint mailing list [email protected] http://lists.reactivated.net/mailman/listinfo/fprint
