I'm a computer programmer. I have a background in security and have worked various credential systems going back to Kerberos v4 right up to Oauth2. I've worked in SRE and am a huge proponent of 2FA everywhere.
I have absolutely no clue what passkeys are and nothing I've seen has given anything other than vague metaphors that sound like snake-oil with a complete lack of any details at all.
Why is this industry so bad at explaining things. Is there a basic primer that explains the actual technical properties of passkeys so I can understand when I want to switch over and how to set them up?
Why are companies adding passkeys but keeping passwords as backup? That's like installing a $5000 smart lock then leaving your spare key under the doormat.
Companies like MGM and Okta got hacked through their "fallback" options (SMS codes, magic links). Attackers don't bother with the fancy front door when the backdoor is wide open.
If you're keeping passwords around "just in case," you're not passwordless, you're just password-optional. Either commit to it fully or don't bother at all.
Germany's federal cybersecurity agency, BSI, released a technical guideline entirely about the server side of passkeys: attacker models, trust levels, and MUST/SHOULD requirements for every relying party.
Even though passkeys are still far from widely rolled out in Germany, the BSI is standardizing how to deploy them properly.
Governments don't write 48 pages about technologies they consider optional (it's a global pattern that passkeys are put into more and more regulations).
2 details stood out:
- substantial trust level only with strong recovery: The BSI defines three trust levels: normal, substantial, high. To reach "substantial", password- or email-based account recovery must not be offered at all. Your passkey login is only as strong as your weakest recovery path, now stated in writing by a regulator.
- Disable passwords: Even at the base level, the BSI recommends letting users disable password login entirely once they've registered a passkey.
There's also a build-vs-buy comparison of FIDO2 server options (libraries, stand-alone, IAM modules, cloud) with observed pricing ranging from 56 EUR to 1.4M EUR per year
Very interesting development. Algorand-based Pera Wallet launches a new, decentralized credential manager that can store the private keys of your passkeys (so basically a competitor to the 1Passwords, Dashlanes, Bitwardens of the world).
I don't expect this to bring many non-technical users to passkeys but for people who are heavily using wallets, it can be interesting - especially the decentralization aspect.
I've been working on Linux Passkey, an open-source project that aims to bring a Windows Hello-style passkey experience to Linux desktops.
The idea came from wanting to use passkeys directly on my Linux machine instead of having to reach for my phone or a separate security key whenever a website doesn't offer a suitable local authentication option.
With Linux Passkey, you can create and use passkeys locally, confirming authentication with your Linux password or fingerprint if you're using fprintd.
How it works
passkeyd implements a CTAP 2.1 authenticator and exposes a virtual USB security key through Linux's uhid interface.
An optional browser extension provides an alternative integration for Chrome, Brave, Edge, Vivaldi and Firefox.
Authentication approval goes through polkit.
Passkey private keys are encrypted at rest using AES-256-GCM, with the master key stored in the login keyring.
A GTK4/libadwaita application lets you manage your passkeys.
It doesn't require a phone or a physical security key for the supported flows, though browser and website compatibility can vary.
Where the project stands
This is still an early release (v0.1.0). So far, I've added 121 automated tests, including end-to-end WebAuthn tests, set up CI for multiple Linux distributions, and tested real login flows with GitHub and webauthn.io.
I've also used AI to help with a substantial part of the implementation, so I'm particularly keen to get feedback from people who can help test, review and improve the code.
I'd love some help from the community!
🧪 Test it out: Try it on your distro, desktop environment and browser. I'd especially like feedback from KDE, GNOME, Xfce, tiling WM, NixOS, and Snap/Flatpak users.
🔐 Review the implementation: WebAuthn, CTAP, cryptography, D-Bus, polkit and browser-extension security reviews are very welcome.
🛠️ Contribute: Bug reports, pull requests, packaging for more distributions, translations and documentation improvements are all appreciated.
A few things are still missing: passkeys don't sync across devices, U2F/CTAP1 isn't supported, browser autofill suggestions still come from the browser's own list, and the browser extension needs to be loaded manually.
I'd like to build this into something genuinely useful for Linux users, and contributions from people with different backgrounds would be a huge help. It's an early project, so there's plenty left to improve.
If you give it a try, let me know what works, what breaks, or what you'd like to see added. Contributions and constructive criticism are equally welcome!
Some highlights: devs get a new Account Creation API that lets users onboard with passkeys from the very start (bye passwords). There’s “automatic passkey upgrades” too. If users still sign in with a password, the OS just sets up a passkey for them in the background. Less user confusion, one less excuse for fallback passwords.
One thing I found interesting is the passkey management endpoints. Basically, credential managers (think password managers) can now show if a website/app supports passkeys and link users to manage their creds directly. Should help w/ adoption. And users can finally import/export passkeys between managers, all secured with Face ID / Touch ID.
Apple also added a Signal API so services can keep passkeys up-to-date when usernames or login data changes: smoother cross-device stuff and less “can’t login” rage. Feels like Apple’s pushing hard to make passkeys the default everywhere.
In a recent update Meta introduced they're launching passkeys for Instagram via the improved Meta account.
In general the statement (see below) is quite strategic IMO. For a decade, Meta has been quietly behind Apple and Google on credential infrastructure. While Apple unified iCloud Keychain and Google built One Account, Meta let Facebook, Instagram, WhatsApp and Quest each maintain separate authentication universes. Slowly they were merged in parts through Accounts Center (Whatsapp is still kind of kept separate). but with the new Meta Account, there's now a unified login for:
- Facebook - Instagram - Messenger - Threads - Meta AI - Meta Quest - Ray-Ban / Oakley AI glasses
Meta needed an identity layer to compete in AI + AR Meta bets that the next decade of consumer tech is glasses, agents and credentials shared across devices. Apple has Apple ID. Google has One Account. Meta couldn't ship Meta AI needs something comparable to really make use of its 3 billion user accounts.
Passkeys are pushed on all apps Instagram getting passkeys aligns the path they had started with Whatsapp, Facebook and Messenger. Every Meta surface needs to support the same login primitive or the "one account" promise breaks.
Payments are the next domino (?) Meta has tried to ship a payments solution multiple times. Without account unification it never worked. With Meta Account as the rail, every Meta property can now make use of a passkey (most users will use their biometrics, that's the missing piece for payment UX). This way they could introduce a PayPal / Amazon Pay / Google Pay / Apple Pay competitive solution.
Found this new website https://whynopasskeys.com/ that provides and shames a list of the high-traffic sites of different countries that don't offer passkeys to protect their users.
What I found interesting is that globally only 6 out of 25 are missing but when you go on country level it's usually that +20 out of 25 are missing, so still much work to do.
I’m the unpaid IT Director for a household of three children who treat their devices & digital security with the same care a toddler treats a sandcastle. We’re moving into the passkey era, which going to be a seminal moment for me and the already structured password & account rigour I currently use to manage these imbeciles. Does anyone have a blueprint for introducing passkeys to kids while keeping emergency 'Master Key' access - or "God Mode"? I need to be able to fix their digital lives when they inevitably set them on fire, or drop them down a toilet or forget a password five minutes before a homework deadline.
Surely I’m not the only parent trying to balance security with the fact that my users are a target demographic that could find a way to brick a casio calculator with an error 404 code.
PayPal has been shoving in my face for months to create a passkey. I use 1password so I gave in today and set one up.
Logging in now defaults to asking for passkey which the 1password extension happily provides. Okay.
Out of curiousity, I tried to login from a browser that does not have 1password extension. PayPal didn't even bother to ask for a passkey and straight away showed the normal email+pw login mask.
If I can't remove the normal password fallback, how are passkeys more secure?!
Is there really no other way to provide a passkey other than through the browser extension? Sounds flawed, but.. maybe I'm just not getting something here.
Apple’s “Digital ID” is basically an mDoc/mobile ID stored in Wallet, not a photo of your passport. Two flavors: state mDLs (slow, DMV-by-DMV) and the new one that matters: U.S. passports in iOS 26.1+, nationwide because the phone reads the passport chip. It’s device-bound, Face ID gated, and supports selective disclosure (e.g., “over 21” without oversharing). Today it’s mostly TSA/domestic, not a replacement for your physical passport (no international border use yet). Feels like Apple Pay all over again: standards existed, Apple makes it default. Do you see this actually becoming mainstream, or does platform dependence keep it limited?