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

Technology

76774 readers
3020 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
[–] Doccool@lemmy.world 39 points 2 days ago (4 children)

Currently I use a FOSS (I think?) password manager, BitWarden, that supports passkeys. I use it across Mac, Windows and Android so I'm while my passkeys are locked yo the password manager, I am not locked to any of the aforementioned megacorps.

[–] SkaveRat@discuss.tchncs.de 22 points 2 days ago (2 children)

While I use and love bitwarden, it's not exactly foss. Although there is a foss implementation of their server backend

[–] AbidanYre@lemmy.world 27 points 2 days ago

Vaultwarden (the free server implementation) also supports passkeys.

[–] kjetil@lemmy.world 5 points 2 days ago

A cursory search lead to this thread from 2024 https://community.bitwarden.com/t/concerns-over-bitwarden-moving-away-from-open-source-what-does-our-future-hold/74800

where an employee stated

I’ll note that policy wise nothing changed. The referenced issue is a packaging bug, but the goal still is the dual licensing model, with the core being open source, and some (mostly enterprise) features being source-available.

Both the client and server are mostly open source. Some server features are paywalled. The alternative Vaultwarden server is fully open source, and much lighter on system resources.

Have there been any recent licensing shenanigans with BitWarden?

[–] kjetil@lemmy.world 10 points 2 days ago

I use BitWarden too. OS , device and browser agnostic is a win

But I imagine the vast amount of people will use whatever their platform is pushing, so Apple Google or Microsoft. And in 5 years time "3rd party passkeys" are not "secure enough" and blocked by the OS. (Ok that's a bit tinfoil hat, but Google's recent Android app developer verification scheme is fresh in mind)

[–] Septimaeus@infosec.pub 12 points 2 days ago

KeePassXC has begun rollout of their own implementation, and I’m pretty sure they’re considered FOSS.

From a quick scan of the white paper, it appears they’re currently using on-device passkey discovery and otherwise “intercepting” passkey registration workflows, which I take to mean they aren’t originating the request as a passkey registrar. This may be the easiest method to satisfy FIDO’s dID requirements.