Comment on Passkeys Explained: The End of Passwords
Netrunner@programming.dev 5 months ago
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.
You still need 2fa I think most passkey implementations incorporate multiple factors already. The session factor is considered distinct from the device factor, even if it’s all on the same device.
Which isn’t super different from the traditional USB key procedure, where a user would activate a FIDO biometric after clearing an SSO portal, or what have you.
Passkeys are cool but you still need 2fa.
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.
Obviously not the personal password, but sometimes you need to share a password. Think about the password for a remote desktop your team may need to connect to for troubleshooting a problem for example.
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…
share your personal password
We share a password. Then we don’t call it a personal password anymore. Was that your question?
- Built-In Two-Factor Security – Passkey logins use your private key stored on your device and your face or your fingerprint or your PIN. Unlike password, these cannot be easily replicated by a scammer.
This only applies though if it's a per-device passkey that uses a private key stored securely that cannot be exported.
If the private key can be exported, it can be stolen and the factors becomes invalid.
But people also store their private key in cloud solutions (some here mentioned doing that) which just makes the factor invalid anyway, since then it's not device-bound anymore, and it's the device that verifies your identity with those methods.
Like, what if someone hacks the cloud service storing the passkeys and steals them? Not really any different from storing passwords in a cloud, and that one isn't called 2FA either.
The article is only referring to per device keys and passkeys that lock them on that device. In other words, someone would need to be able to get your device’s key, decrypt it or brute your passkey, spoof or steal your device somehow, and send the key under it’s identity. I’m sorry, but I don’t think the few people that could do that would be wasting their time to do it to little old you. For most people, their insignificance is the best security they have.
Isn’t this optional? I use passkeys and have yet to be asked for anything else in addition to it.
I’ve only ever seen passkeys used as 2FA, personally.
Really? If I open github (for example) and select passkey login, I just need to press ok using Bitwarden.
Zak@piefed.world 5 months ago
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.