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
Passkeys are cool but you still need 2fa. Which may as well be a passkey itself.
One factor is not great even if it’s a passkey.
Need is a strong word.
2FA is a pretty good idea for some applications and needless hassle for others. I don’t need most of my accounts to have 2FA; I use a password manager with strong unique passwords, and for many accounts, having to make a new one would be an inconvenience rather than a tragedy.
Service providers might be motivated to force it on me if stolen accounts could cost them money, but most of them don’t need to; it’s just the most expedient move for them.
How do you use it then if you need to share access in the whole team?
You don’t share your personal password across the whole team now, do you? At least for your teams sake I hope you don’t.
You know that not every account is only used by a single user, right?
I think that’s the problem right there… If you share accounts across multiple people you have far greater problems than how passkeys work…
Or they’re using it as intended. I’ve had more than one account I’ve gotten by cost sharing with friends. That’s not a problem, that’s a solution.
And it only takes one person with a grudge to cause a problem. I have seen it. I have shared accounts but very carefully and if someone abuses it then they permanently lose access to my stuff even if they are family.
We share a password. Then we don’t call it a personal password anymore. Was that your question?