On 1 March 2008 23:34:30 Daniel Drake wrote: > Hi Vasily, Hi, Daniel
> Sorry for the delay in getting to this. Congratulations (and thanks) for > being selected to work on fprint as your university project. I've interested in it too ;) > Out of interest, do you have to do any writeup as well as the actual > coding? If so, will you be publishing it? > > For my own project I have to write a big report and plan to publish it > under a creative commons license in early May. Well, I have to, at least for university, so if it will be usefull for anyone I'll translate it to English and publish it ;) > > Sorry, last patch introduced regression for devices that do not support > > identification. New one fixes that. > > Can you combine this patch into one? "git commit --amend" and "git > rebase --interactive" are helpful tools here :) > > The patch seems a bit messy in that it creates a gallery even for prints > that do not support identification, and it also is a bit confusing > code-flow wise. For example do_identify() calls fp_verify_finger() on > devices that don't support identification. Yep, I really don't know what to do with devices that don't support identification :( So now pam_fprint creates full gallery, and if device doesn't support identification, uses only first fiingerprint for verify. > Any chance you could give it a bit of a rethink? I'd envision some kind > of dual codepath system depending on whether the device supports > identification or not, with some helper functions to simplify the common > parts (such as interpreting results). > > FYI, in the long term I am thinking about folding identification and > verification into just one function (identify), and allowing drivers to > place an upper limit on the gallery size. Devices that can't do > identification would set this limit to 1. > > Thanks! > Daniel I've heard that you're writing authentification daemon, or something like that, if it's so, when it will be available for public? I'm asking because now I'm encountering problems with blocking nature of fp_identify and fp_verify functions (I can detail it if you want ;)). Maybe you've seen a part of discussion with Marcin about that on maillist... Btw, now I'm going to redesign pam_fprint a little bit. It should use auth daemon through dbus, and same daemon should be used by several kde apps, like kdm, kwallet, etc. I think we should open discussion about libfprint integration on maillist, or (better) on irc ;) There's too much opened questions ;) Regards Vasily _______________________________________________ fprint mailing list [email protected] http://lists.reactivated.net/mailman/listinfo/fprint
