this post was submitted on 11 Nov 2025
290 points (87.6% liked)

Technology

76774 readers
3196 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years ago
MODERATORS
 

Passkeys are built on the FIDO2 standard (CTAP2 + WebAuthn standards). They remove the shared secret, stop phishing at the source, and make credential-stuffing useless.

But adoption is still low, and interoperability between Apple, Google, and Microsoft isn’t seamless.

I broke down how passkeys work, their strengths, and what’s still missing

you are viewing a single comment's thread
view the rest of the comments
[–] sonofearth@lemmy.world 2 points 1 day ago* (last edited 1 day ago) (1 children)

But what’s dystopian about passkeys? They are actually more secure than Password + TOTP. Phishing out a passkey is practically impossible.

[–] TotalCourage007@lemmy.world 1 points 18 hours ago (1 children)

If its not fully functional it feels more like a vendor lock in than anything actually useful. Use a Google device but want to change? Oh I'm sorry you have to do all this work first thanks to passkeys.

Some websites are better about it but they can also have support in-fighting over which service works better. Its the Password Manager scenario all over again but worse.

[–] sonofearth@lemmy.world 1 points 17 hours ago

That’s why it’s important to avoid vendor lock-in and use actual reputable password managers to secure your passkeys such as Bitwarden, 1Password, or KeePass. On Android 14+ and iOS, you can even set your preferred password manager as the default passkey provider.

If you don’t fully trust Bitwarden servers, you can self-host a Vaultwarden instance, which is compatible with Bitwarden clients. Alternatively, using a yubikey is also a great hardware based option. Just because Google & Microsoft are heavily promoting passkeys doesn’t mean they’re inherently bad.

Passkeys work flawlessly for me across platforms:

  • Android 14–15 (except on Brave with de-Googled devices)
  • iOS 17–26 (and likely beyond)
  • Windows 11
  • Linux; while it doesn’t have OS-level integration yet, passkeys work perfectly in modern browsers

Personally, I use passkeys everywhere. I host my own Vaultwarden instance to store all my passkeys, and for redundancy, I also keep separate ones in my Keepass database, which I use for TOTPs. My self-hosted stack is secured by Authentik, running completely passwordless and uses passkeys for authentication and other apps integrate via OAuth and Proxy Auth.

I still don’t quite understand the issue you mentioned with websites. Typically, the passkey mechanism is triggered directly by the browser or OS (if you’re on mobile). You’ll be prompted to either save a new passkey or sign in with an existing one. If your password manager is correctly set up as the default credential provider, it should work seamlessly. Even without a browser extension, most Chromium-based browsers let you scan a QR code with another device that has your passkeys or you can simply insert a yubikey to authenticate.

What infuriates me is that some services like Amazon use passkeys only as second factor and asks for an OTP anyways which defeats the whole purpose. But for services that do it right, passkeys works seamless!