What 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
alvvayson@lemmy.world 1 year agoBitwarden is also supporting passkeys, so it won’t make a difference for their users whether they use passwords or passkeys.
And the fact that you don’t see anything wrong is more a you problem. Boomer mentality, dude. Don’t became one.
V0lD@lemmy.world 1 year ago
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:
- XSS bug in the target website
- Browser vulnerability
- Malicious browser (not a concern on iOS but a concern everywhere else)
- Compromise of any cert in the chain between you and the target website
- Convincing the user to install (or using malware to install) a root certificate, or compromising one you already installed (e.g., for work)
- Bookmarklet/clipboard/devtools attacks
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.
Engywuck@lemm.ee 1 year ago
Boomer you mom, idiot. Fuck off.
Kusimulkku@lemm.ee 1 year ago
It would probably be better for you to explain what’s wrong and not just call them a boomer as if that explains it.
alvvayson@lemmy.world 1 year ago
If they want to be a Boomer and stick to 20th century solutions, why should I care?
If it works for them, fine. Nothing wrong with that.
It’s obviously not working for most people. Most people reuse weak passwords and get their passwords hacked. Passkeys solve that for those users.
That’s why the whole industry is shifting to passkeys.
Kusimulkku@lemm.ee 1 year ago
“It’s old so it’s bad” is not a very convincing argument.
I think he was wondering how technically the new solution is better, especially compared to password database solutions where complex password and password reuse isn’t an issue.
alvvayson@lemmy.world 1 year ago
I said the exact opposite. If the old thing works for you, go ahead and stay on it, but don’t complain about the rest of the world improving and moving forward.
Why put quotes when you are misquoting…
And I answered him, he just doesn’t want to know. I can’t solve that.
Natanael@slrpnk.net 1 year ago
Webauthn has domain bindings and single use challenges which prevents MITM credential stealing, etc
wildginger@lemmy.myserv.one 1 year ago
It kinda sounds like you dont actually know whats wrong, and are just blindly following the trends.
Doesnt that make you the boomer?
alvvayson@lemmy.world 1 year ago
Sure. I am become the Boomer lol.
HubertManne@kbin.social 1 year ago
oh man. so I am a boomer. good to know.