Fingerprint Login on Linux with fprintd
If your laptop has a fingerprint reader, there is a good chance it works on Linux. Support comes from libfprint, a library of drivers for readers, and fprintd, a service that desktops and PAM use to ask for a fingerprint.
Is your reader supported?
Find the reader’s USB ID:
lsusb | grep -iE 'finger|synaptics|elan|goodix|validity|egis|focal'
Bus 003 Device 004: ID 06cb:00fc Synaptics, Inc.
Look up the ID (here 06cb:00fc) in libfprint’s supported devices list on its project site. Readers in business laptops, such as ThinkPads, Dell Latitudes, and Framework laptops, usually work. Some consumer laptops use readers with no Linux driver, or a vendor driver that only some distributions package.
Install the packages, which most desktop installs already include:
sudo apt install fprintd libpam-fprintd # Debian / Ubuntu
sudo dnf install fprintd fprintd-pam # Fedora
Then check that fprintd sees the reader:
fprintd-list $USER
Enrol a finger
GNOME: Settings, System, Users, then turn on Fingerprint Login and follow the prompts.
KDE Plasma: System Settings, Users, then your account and the fingerprint option.
Terminal:
fprintd-enroll # right index finger by default
fprintd-enroll -f left-index-finger
fprintd-verify # test it
fprintd-delete $USER # remove all enrolled fingers
You will touch the reader five to ten times while it builds a template. Enrolling two fingers, one on each hand, helps when one is injured or a device is in your other hand.
Use it for login, unlock, and sudo
GNOME and KDE use fingerprints for the lock screen and login screen automatically once enrolled. For sudo and other PAM services, enable the fingerprint PAM module:
Ubuntu and Debian:
sudo pam-auth-update
Tick Fingerprint authentication.
Fedora and RHEL:
sudo authselect enable-feature with-fingerprint
sudo authselect apply-changes
Now sudo prompts you to touch the reader, and falls back to the password if you press Ctrl+C or it fails. Do not edit /etc/pam.d/ files by hand on these systems; the tools above manage them, and our PAM explainer explains why.
The keyring caveat
Your desktop keyring (GNOME Keyring or KWallet), where browsers and apps store passwords, is encrypted with your login password. A fingerprint cannot decrypt it. So after logging in with a fingerprint, you will be asked for your password the first time an app needs a stored secret.
Many people settle on: password at login, fingerprint for the lock screen and sudo. That keeps the keyring unlocked automatically and still saves typing during the day.
Security considerations
- Fingerprints are not secrets. You leave them on everything you touch, and you cannot change them if they are copied
- Someone can press your finger on the reader while you are asleep or coerced
- Match-on-chip readers store and compare the fingerprint inside the sensor, so the template never reaches the computer; others store templates in
/var/lib/fprintand match on the host - A fingerprint never replaces your disk encryption passphrase, which protects the machine when it is off; see our disk encryption guide
For stronger second factors over SSH, our SSH two-factor guide covers TOTP and FIDO2 keys.
Troubleshooting
systemctl status fprintd
journalctl -u fprintd -b
- “No devices available”: the reader is not supported by your libfprint version; check for a newer version or a vendor driver
- Enrolment fails repeatedly: clean the sensor and try another finger
- Works at the lock screen but not after suspend: some readers need a firmware update, available through fwupd on supported laptops
Frequently Asked Questions
Does my fingerprint reader work on Linux?
Check with lsusb to find the reader’s USB ID, then look it up in libfprint’s list of supported devices. Many Synaptics, Elan, and Goodix readers work, especially in business laptops. Some readers have no driver, or only work with a vendor-specific driver.
How do I enrol a fingerprint?
In GNOME, open Settings, System, Users, and turn on Fingerprint Login. In KDE, use System Settings, Users. From a terminal, run fprintd-enroll, touch the reader several times when prompted, and test with fprintd-verify.
How do I use my fingerprint for sudo?
On Ubuntu and Debian, run sudo pam-auth-update and enable Fingerprint authentication. On Fedora and RHEL, run sudo authselect enable-feature with-fingerprint. After that, sudo asks for a fingerprint first and falls back to the password.
Why does it still ask for my password after fingerprint login?
Your login keyring is encrypted with your password, and a fingerprint cannot decrypt it. After logging in with a fingerprint, the desktop asks for your password the first time an app needs a stored secret. Some people therefore log in with a password and use the fingerprint for unlocking and sudo.
Where are fingerprints stored?
fprintd stores enrolled templates under /var/lib/fprint, readable only by root. Some readers store and match the fingerprint on the sensor itself instead, which is more secure because the template never reaches the computer.
Is fingerprint login secure?
It is convenient but weaker than a strong password in some ways: fingerprints are not secret, cannot be changed if compromised, and someone can press your finger on the reader. It is reasonable for unlocking a laptop, but keep a strong password for disk encryption.