mirror of
https://gitlab.com/mishakmak/pam-fprint-grosshack.git
synced 2026-04-08 20:03:34 +02:00
872089883c
Add scripting capabilities to the verification process so that the mock daemon can send its own results without needing the client to prod it to do that. This is incredibly useful when the client is single threaded and blocking. Note that there are barely any safeguards, so the scripting task is not cancelled if an error occurs, or the VerifyStatus signals are sent out of order.
fprintd ======= https://fprint.freedesktop.org/ Daemon to offer libfprint functionality over D-Bus Might eat your kangaroo. Written in C. Licensed under the GPL version 2 or any later version (see COPYING). A PAM login module is included in the 'pam' directory. 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