mirror of
https://gitlab.com/mishakmak/pam-fprint-grosshack.git
synced 2026-04-08 20:03:34 +02:00
69c131f723
This is a gross hack for PAM sessions to work as expected. root is allowed to verify any users. If you want to allow any other actions for root, you'll need to go through normal PolicyKit procedures. This should fix fingerprint authentication not working in GDM, or on the console.
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). An experimental PAM login module is included in the 'pam' directory. This will be moved to a separate package once the system has matured. 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