Still very much wanted on Linux. Here are some specifics that might help move it along. The standard way to do this on Linux is polkit, and the other big password managers already ship it. 1Password, Bitwarden and KeePassXC (Polkit Quick Unlock, in 2.8) all unlock through polkit. polkit hands the check to PAM, so the user’s existing system configuration decides what’s accepted: fingerprint via pam_fprintd, password, or a security key. The app never handles biometric data; it just gets a yes or no back. It wouldn’t change Enpass’s security model. Quick Unlock with a PIN already works this way: the master password is required at app launch, and after that a short check releases the key held in memory. A polkit check could stand in for the PIN prompt; no new key storage or cryptography is needed. 1Password describes its Linux implementation exactly like this (“stays in the memory while 1Password is running… removed from memory when you quit”). What it takes: a .policy file shipped in the package, plus a D-Bus call to org.freedesktop.PolicyKit1.Authority.CheckAuthorization. Enpass already uses D-Bus on Linux (logind, KWallet, Secret Service), so the plumbing is there. A question for the team: the Linux build I’m running (6.12.6.2258, Fedora 44, KDE Plasma 6) already contains the string “Unlocks Enpass using the biometrics on your Linux system.” Is Linux biometric unlock actively being worked on, and is there a rough timeline? I’m always happy to test.