Comment on Google will now make passkeys the default for personal accounts
V0lD@lemmy.world 1 year agoWhat do you see that’s wrong with it that we don’t if I may ask?
Comment on Google will now make passkeys the default for personal accounts
V0lD@lemmy.world 1 year agoWhat do you see that’s wrong with it that we don’t if I may ask?
DeadlineX@lemm.ee 1 year ago
Mostly phishing. Passkeys can’t be phished. And really, passwords are awful in general for security purposes. You don’t have to use your phone or google or apple or whatever.
I actually have a physical usb key that I use as a passkey. Its just a more secure login implementation and will likely be the only option in the future.
hedgehog@ttrpg.network 1 year ago
Passkeys can be phished, it’s just much more difficult than with passwords, TOTP MFA, SMS MFA, other OTPs, or push notification-based MFA (e.g., Duo or the way Microsoft, Apple, and Google push a notification to their app and you confirm and/or enter the key).
Passkey is extremely phishing resistant in the same as Webauthn MFA and U2F MFA are, in that origin checks by the browser prevent attackers from initiating the auth process. But it can still be attacked in these ways:
From memory, passkeys, webauthn, and u2f should prevent over 99% of phishing attacks that are successful without them in place.
There’s also the risk of the passkey itself being compromised, though that level of risk is dependent on your device / how you’re storing your passkeys and isn’t a “phishing” risk.
Natanael@slrpnk.net 1 year ago
The main point is all those attacks need to attack the local software or hardware implementation on one of the two ends (or a cert issuer), and even then it’s replay protected so for example an XSS attack lasts only for one session, so it’s more robust.
hedgehog@ttrpg.network 1 year ago
Correct, but that doesn’t change the fact that “Passkeys can’t be phished” is not true.