- cross-posted to:
- linux@lemmy.ml
131
- cross-posted to:
- linux@lemmy.ml
Ricky Mondello (@rmondello@hachyderm.io)
hachyderm.ioIf you actually read the “Passkeys are a trap. Do not use them.” post going around, you’ll find a transparent attempt to clumsily string together a conspiracy.
The post is predicated on the idea that a feature of WebAuthn called “attestation”, which is only used in high-assurance and usually corporate scenarios, and usually with physical hardware security keys, will be leveraged to hurt people, somehow.
The post posits that a website like X will bait and switch users: first, you get a passkey. Then, later, scary “attested” passkeys! This simply isn’t possible to do because attestation isn’t supported on the web for mass market, consumer authentication.
Attestation for passkeys (software-based, syncable credentials) is antithetical to their mass market goals, and would freeze out independent, non-corporate-backed credential managers. It’s an explicit non-goal of the designers of passkeys, who work together in a forum anyone can join.
And trust me, websites and apps like banks repeatedly asked for attestation at the beginning of the industry’s passkey journey. The platforms, browsers, and credential management apps have held firm that the goal of passkeys is reducing phishing and **not** some kind of trusted computing scheme. (And I will note: over my dead body!)
Besides the theory of the case being fundamentally wrong, there are several things that make the post disqualifying in terms of arguing something useful or important in the realm of security, privacy, and user authentication:
1. Intentionally presenting things that are complicated as inherently suspicious. (Delivering security by design can be complicated, yes!)
2. Describing TOTP as a “great solution” for adding security to a password-based account. When the most common threat model on the web is phishing (a word the post never mentions!), TOTP hardly buys you _anything_. TOTP is phishable.
3. Seeming to be unbothered by how many logical leaps are being taken without actually understanding the topic being discussed.
There are bad things happening in tech and untrustworthy people and companies do exist, but they’re largely in the AI space, not the “let’s stop people we love from getting compromised through phishing” space.
A rebuttal to an anti-passkey, pro-TOTP post that has made the rounds on Lemmy as well.


Nah, lock-in is not a safety feature. 16+ random chars are plenty, and if cracking gets better I’ll go to 20 or 30 chars. My pw manager doesn’t care what strings go in it or which device opens it up.
You can have passkeys on multiple devices. I use them on different platforms for the same sites.
How do you transfer your passkey to a new device?
If you use a self-hosted password manager like bitwarden, then its there. If you use a file-based password manager like keepass, then you can use any syncing method you choose, and its no different from passwords.
not sure about every OS but the ios password app has a menu button to export them to other apps. I have exported mine to my own self hosted vaultwarden. took 2 minutes
You don’t, you can have multiple passkeys, one for each device.
ok.
How do you add a new device to your account without a password or the old device?
Password, then get a prompt about registering a new passkey.
After that I can use the passkey registered on either device.
Edit: to clarify, most sites still let you log in with a password after you’ve registered a passkey
The the account is still as vulnerable as a password.
Yes, but you’re less susceptible to phishing when you login with a passkeys.
It’s also makes logging in faster.
That’s my workflow as well 26 random characters, a yubikey (and Aegis TOTP for sites that don’t have fido or similar) and I’m good.
I like the idea of a Yubikey but there is no way it would survive more than a month on me due to the conditions where I work. And getting a physical key then not having it on my body at all times is a non-starter.
I keep my keepass .kdbx in on a webdav server and that covers any device I can think of.
Do you work in a blender? It’s a pretty solid bit of plastic, should be fine in a pocket or wherever the device you’re using it with is.
Maintenance at a blast furnace. I am exposed to acidic vapours, caustic vapours, ambient heat in the 60c range, radiant heat in the 1000c range, rock from the nanometer up to 30cm size, phenolic resins, oil mists, and metal powders. And then there’s the crawling around over, under, and between equipment.
Not every tech-savvy person works in an office.
Cool. Hope it’s ok on your health. I suppose you have some way to keep your phone safe, and don’t need to do 2FA while exposed to all of those things. You could probably wrap one up pretty well and still have the NFC work too.
Totp with a backup of the secrets/seed qr stored in a kdbx. If my phone melts it’s a 24hr problem at most.
Passkeys also aren’t lock-in. You control them, and your FOSS password manager likely already supports them.
you are required to use a 3rd party. that third party has control. you can’t switch. that is lock-in.
I’m using a FOSS password manager for like 6+ passkeys right now, on some of the biggest sites. So this is just demonstratably false.