r/BuiltWithClaude • • Oct 20 '26

Linux Passkey implementation

Hey All,

Windows has Windows Hello and macOS has Touch ID, but Linux has no built-in passkey authenticator. When a site offers “Create a passkey”, Linux users get sent to their phone or a USB security key, and some sites (GitHub, for one) warn about “partial passkey support”.

So I built Linux Passkey. It makes your computer the authenticator:

A website asks to create or use a passkey.

A prompt pops up: “Create a passkey for github.com?”

You confirm with your normal Linux password, or your fingerprint if you use fprintd.

No phone and no hardware key, and the “partial support” warnings go away.

How it works (short version)

passkeyd is a small user service that acts as a CTAP 2.1 authenticator. Browsers see it as a virtual USB security key (through the kernel’s uhid), so it works in every browser even without an extension.

An optional browser extension (Chrome, Brave, Edge, Vivaldi, Firefox) makes it a built-in authenticator, the way Windows Hello is.

Verification goes through polkit, never cached, so it’s your system’s own password/fingerprint dialog.

Private keys are encrypted at rest (AES-256-GCM) under a master key stored in your login keyring.

A GTK4/libadwaita app manages your passkeys. There’s an optional GNOME Shell extension, but it works fine on KDE, Xfce and others.

Install: signed apt, dnf, zypper and pacman repos for Debian/Ubuntu, Fedora/RHEL 10, openSUSE Tumbleweed and Arch:

👉 https://packages.akileswar.com/linux-passkey/

Source (MIT): https://github.com/HaythmKenway/Linux-Passkey

Being upfront: I vibe-coded a big chunk of this with AI. I’ve tested it as much as I can:

121 automated tests, including end-to-end WebAuthn tests.

CI builds the packages and installs them on Ubuntu, Fedora, openSUSE and Arch.

I’ve used it for real logins on GitHub and webauthn.io.

But it’s v0.1.0, and it handles your logins, so please be skeptical and poke holes in it. Reviews of the crypto, the D-Bus interface and the browser-extension origin checks are especially welcome.

Where I’d love help

🧪 Test it on your distro and desktop. KDE, Fedora, Arch, NixOS, tiling WMs, GNOME 50, fingerprint readers: tell me what breaks.

🦊 Snap and Flatpak browsers. The virtual USB key can be hidden from snap browsers; I’d like to hear how it goes for you.

🛠️ Contribute. Issues, PRs, packaging for more distros, translations. I’d really like to build this with people who know this stack better than I do.

Known limits: passkeys stay on one device (no sync), autofill suggestions still go to the browser’s own list, there’s no U2F/CTAP1, and the browser extension isn’t on the stores yet (you load it unpacked for now).

Thanks for reading. Feedback, roasts and bug reports are all welcome 🙏

1 Upvotes

0 comments sorted by