mirror of
https://gitlab.com/mishakmak/pam-fprint-grosshack.git
synced 2026-04-08 20:03:34 +02:00
4f3589c0dc
We run a certain number of tests right now, without being able to easily run them separated or to check which one failed. So add a script to inspect all the available unittests per each python script and use it to figure out the tests we can run in meson. As per this, define a global 'python_tests' variable in meson that allows to register new python tests easily without having to repeat the settings for all the tests. For each test we have, we check if we can fetch a list of unit tests, and if possible we create a meson test for each one. Otherwise we just fallback to normal behavior. This is something that can be hopefully implemented into upstream meson [1]. [1] https://github.com/mesonbuild/meson/issues/6851
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