libfprint is an open source software library designed to make it easy for application developers to add support for consumer fingerprint readers to their software.

Features

• Written in C
• Licensed as LGPL-2.1
• Depends on libusb for USB communication and glib
• Primarily developed for linux, but should be fairly portable
• Offers a single API to application developers to access the entire range of supported devices
• Supports imaging - downloading live fingerprint scans from the device
• Includes image processing/matching code
• Supports enrollment/verification - enrolling a print from a known user, and then later comparing a live scan to the enrolled print

Useful Links

• FAQ
• Download
• Supported devices
• Unsupported devices
• Installation
• Mailing list - user support happens here
• U.S. Export Administration Regulations info

Driver Info

These drivers are included within libfprint, the corresponding pages are for information only.

• /aes1610: Authentec AES1610
• /aes1660: Authentec AES1660
• /aes2501: Authentec AES2501
• /aes2550: Authentec AES2550 and AES2810
• /aes2660: Authentec AES2660 and EikonMini
• /aes4000: Authentec AES4000
• /fdu2000: SecuGen FDU 2000
• /upeksonly: UPEK TouchStrip sensor-only
• /upektc: UPEK TouchChip and EikonTouch 300
• /upekts: UPEK TouchStrip with biometric co-processor
• /uru4000: Digital Persona U.are.U 4000/4000B/4500
• ?/vcom5s: Veridicom 5thSense

The user-experience quality of these drivers is noted at /Driver quality.

API documentation

API documentation can be found here: http://www.reactivated.net/fprint/api/

It is updated from the source code periodically. To generate your own documentation from the sources, install doxygen then, from a libfprint source tree:

cd doc
make docs

Documentation is then available under the html subdirectory.

Development

libfprint is developed using the git version control system. The git user manual is very useful for new users.

• git://anongit.freedesktop.org/libfprint/libfprint
• View online

Discussions about features, or questions should happen on the mailing list

Contributing

Bug reports and (git formatted) patches should go to the FreeDesktop bugzilla.

See the HACKING file for some information on the code and its design, and TODO for some items that remain to be completed.