mirror of
https://gitlab.com/mishakmak/pam-fprint-grosshack.git
synced 2026-04-08 20:03:34 +02:00
cce9551c98
Some tests may have different behaviors depending on the CPU load when using parallel tests, so async results could arrive in different order. Then we need to accept multiple results: - A specific exception has to happen all the times - One of the accepted exception has to happen all the times - No exception or one of the allowed exception may happen Depending on the test, use one of the possible strategies.
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