mirror of
https://gitlab.com/mishakmak/pam-fprint-grosshack.git
synced 2026-04-08 20:03:34 +02:00
e8c36e9592
- Remove SetUsername itself, and add a username parameter to DeviceClaim, ListEnrolledFingers and DeleteEnrolledFingers. - For each of those calls, check that the incoming connection is allowed to operate on that particular username - Don't require a claimed device to list or remove fingerprints - Clean up username and sender when releasing the device - Modify the storage backend to not require an opened device to list or delete fingerprints - Add a simple test program to list registered fingerprints for the usernames passed as argument
fprintd ======= http://www.reactivated.net/fprint/wiki/Fprintd Daemon to offer libfprint functionality over D-Bus Currently in early stages. Might eat your kangaroo. Written in C. Requires bleeding edge libfprint (libusb-1.0 port). Licensed under the GPL version 2 (see COPYING). API use cases ============= - User wants to use the fingerprint reader, and enroll his fingerprints, or remove some fingerprints from the database - Administrator wants to enroll fingerprints for a particular user, or remove fingerprints for a particular user - Laptop/desktop authentication: * Check for fingerprint devices * Check whether a particular user has any fingerprints enrolled * Verify a fingerprint for a particular user, or, if the device supports it, verify that the fingerprint matches against any of the fingerprints enrolled - 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