290
Passkeys Explained: The End of Passwords (sentientrant.com)
submitted 1 year ago by to c/technology@lemmy.world
204 comments fedilink hide all child comments
 

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
[–] [S] -4 points 1 year ago (2 children)

Even if you are really careful, your details can always be leaked from a company server during a breach. If the companies adopt passkeys, that issue isn't there. Because there isn't a password anyone can randomly use. That's why I feel big tech companies are moving towards it.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 1 year ago

    Companies should already be storing password hashes, so the risk of leaking a hash vs a public key is roughly the same. It's just that private keys are generally longer than passwords and therefore harder to bruitforce.

    Any company storing passwords in a recoverable format deserves to be hacked.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 1 year ago

    Yes, you have to trust the company storing the passwords.

    A good company can store passwords in ways that are secure to most hacking attempts. It isn't impossible to break the encryption typically used, but it is difficult enough that most thieves will not have the resources or time to make use of the data. They want the low effort password databases, not the difficult and expensive ones.

  • permalink
  • fedilink
  • source
  • parent