From Fedora Project Wiki

< Features

Revision as of 06:26, 11 July 2008 by Kkofler (talk | contribs) (Mention that Rawhide already has libusb1.)

The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

Fingerprint Readers

Summary

The goal of the project is making fingerprint readers as easy as possible to use for authentication (primary or secondary).

Owner

  • Name: JosePlans, BastienNocera

Current status

  • Targeted release: Fedora 10
  • Last updated: 2008-06-01
  • Percentage of completion: 25% (planning)

The fprint package was added to Fedora CVS (and built ). It is now available for Fedora 7, Fedora 8 and later.

The pam_fprint package has been added to Fedora CVS (and built ). It is now available for Fedora 7, Fedora 8 and later.

The fprint_demo has been added to Fedora CVS (and built ). It is now available for Fedora 7, Fedora 8 and later.

More details on the current status (as of writing, 2008-06-01) are available in Daniel Drake's project report .

Most of the applications of fprint would need fprintd, which requires: libusb-1.0 (async design, not compatible with 0.1, packaged as libusb1 in Rawhide), and the async branch of libfprint.

Detailed Description

Currently, using Fingerprint readers is a bit of a pain, and installing/using fprint and its pam module take more time than should ever be necessary.

Benefit to Fedora

Better Out-of-the-box experience for systems with fingerprint readers.

Scope

Better integration would mean

  • Having a D-Bus service that's a HAL singleton for handling reading/using the fingerprint reader. Potential API (BastienNocera, API needs loads of work). (snipped)
  • Most of the API is already implemented in fprintd, the D-Bus daemon. It uses service activation instead of being a HAL singleton. Identification parts of the API are missing.
  • The PAM module would use the Verify method provided over D-Bus to authenticate users, and will be added to the default configuration.
  • gnome-about-me would use the Acquire method to write a new fingerprint data file for the specified user.
  • gnome-screensaver would be able to use finger scans to unlock the desktop
  • Any other dialog presented to the user for authentication would be able to use finger scans
  • The create-user dialog in firstboot or its replacement could offer to enroll the new user

Test Plan

  • Person installs a laptop/desktop system with a fingerprint-reader that's supported by fprint
  • Person sets their fingerprint in gnome-about-me or in the user creation firstboot module
  • Person can log in using their fingerprint

Documentation

Dependencies

  • Changed backend library from thinkfinger to fprint , after discussion with the maintainers of those two modules.
  • libusb 1.0 (async design, not libusb 0.1 already available in the distribution)
  • async support in libfprint (see above)

Contingency Plan

Not installing the packages by default.

Release Notes

FIXME

Comments and Discussion

See Talk:Features/Fingerprint