GitLab

For verify and enroll, add a done argument so that front-end
know easily when they should be closing the device.

We need to enumerate all the fingers for swipe and press actions,
otherwise we might break break translations.

Better messages for the PAM plugin, by using whether the device
requires swiping or pressing the finger on the reader.

Export the type of scan the device performs, and, when the device
is claimed, the number of enrollment stages.

The clients aren't supposed to know the magic numbers for enums,
so use strings instead.

More done, and more to do.

As we're not using the non-default device anyway.

Gives you the first device listed in GetDevices.

When listing, list all the fingerprints for all the users mentioned on
the command-line for each connected device, rather than just the
default one.

Use well-defined strings instead of numbers to pass around
specific fingers in the public API.

as the rest of our functions.

Add GetProperties method, with a single "Name" properties into
the hashtable.
Use the device name property in the PAM module, and in the list test.

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.

We need to double-check the messages so that they're translated
for users in the UIs.

And add a TODO item

So that we avoid clashing with distribution binaries.

1) Set up our own D-Bus (private) connection
2) Set up our own main loop and main loop context

This means we finally work right within gnome-screensaver!

Track clients connected to each device using EggDbusMonitor.
When there are no more clients connected to the device, release it.

When no devices are used anymore, set up a timeout to exit within
30 seconds.

When no actions are happening on any of the devices, make the
daemon exit after 30 seconds.

Add an action property and notify listeners when the action changes.

Return an error if an enrollment is already in progress.

Track the current action happening in the device, so we can
see what each device is doing. Refuse to launch a verification if
there's already one in progress.

Otherwise it just won't work...

Add a PAM module, and enable all the warnings

..

If the finger passed for verification is -1, always emit the
VerifyFingerSelected signal, as the front-end isn't to know
whether we're using identification or verification.

More warnings fixed in the file storage.

More to do though...

This is better than what we've got currently, and
even works with older versions of GCC.

- Add a finger selected signal, so that when an "automatic" finger
  is selected for verification, we know which one to scan
- Fix the finger print numbers list to use GPOINTER_TO_INT /
  GINT_TO_POINTER
- Make sure the gallery is NULL when there's no prints available
- Don't use identification when a finger number is provided
- Add support for selecting the finger number in verify
- Add support for fatal warnings there as well

Passing -1 to the VerifyStart function will either accept any
fingers scanned, if the driver supports identification, or select
the first enrolled fingerprint for scanning if it doesn't.

ClaimDevice is now only needed for hardware related actions

Remove a few debug messages, and merge another one.

- Remove SetUsername itself, and add a username parameter to DeviceClaim,
  ListEnrolledFingers and DeleteEnrolledFingers.
- For each of those calls, check that the incoming connection is allowed
  to operate on that particular username
- Don't require a claimed device to list or remove fingerprints
- Clean up username and sender when releasing the device
- Modify the storage backend to not require an opened device to list
  or delete fingerprints
- Add a simple test program to list registered fingerprints for the
  usernames passed as argument

Add naive plugin support to the storage code, it will
load plugins from $(libdir)/fprintd/modules, given the configuration
from /etc/fprintd.conf.

This should be used to set the storage type.

We can only delete fingerprints if we could enroll them
in the first place.

Allow enroll and verify to optionally set a username. Makes
testing easier.

Add a few more TODO items