On Wed, 2008-12-10 at 23:25 +0100, Linus Färnstrand wrote: > Yes true. > But I'm not creating an app for the system specifically. So I don't > want prints to be stored as if they were for a user of the system. > This will be an app running as a single user but it will work with > many persons, not users of the system. But users of my specific app. > If I could save prints to my own identifiers for users and then let it > identify amongst them that would be great.
This is something that you can do with fprintd. The users you enroll don't have to exist, but the user that runs the front-end has to have enough permissions in PolicyKit to change the username. Look for "Select a user to enroll" permissions in polkit-gnome-authorization. Is this a Point-Of-Sale system? Did you want to use your front-end to detect which user scanned their finger on the reader to log them in to their tills? Support for POS was planned from the start, although I wasn't sure about the API to use. See the notes in the README: ---8<--- - Point Of Sale authentication (in a bar, the fingerprint reader is used to see who accesses a particular point of sale/till, in place of PIN code authentication and/or tokens) * Given a list of users, verify which one has scanned their finger ---8<--- > But maybe I should just use libfprint directly then? Are there any > python bindings for the async version of the lib? I still think working with fprintd is a better idea, for the reasons mentioned before. And you get Python support for free! _______________________________________________ fprint mailing list [email protected] http://lists.reactivated.net/mailman/listinfo/fprint
