Benjamin Berg fc7e4d0e5c device: Do not require authentication for release/stop
If someone has started an operation, then we don't really need to
confirm they are permitted to stop it again. Not doing this has the
advantage that we cannot run into a second interactive authorization
step accidentally.
2020-12-07 15:14:07 +01:00
2015-02-09 18:11:10 +01:00
2020-12-01 09:00:55 +00:00
2020-11-13 13:32:51 +01:00
2020-02-05 16:54:54 +01:00
2008-11-02 11:16:13 +00:00
2008-12-10 00:54:27 +00:00
2020-12-01 14:22:55 +01:00
2020-12-01 14:22:55 +01:00
2018-06-07 22:25:39 +02:00
2018-05-31 17:28:19 +02:00

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

Description
No description provided
Readme 1.7 MiB
Languages
C 80.9%
Meson 19.1%