- cross-posted to:
- linux@lemmy.ml
- cross-posted to:
- linux@lemmy.ml
A rebuttal to an anti-passkey, pro-TOTP post that has made the rounds on Lemmy as well.
You must log in or register to comment.
“TOTP is phishable.”
i can safely say both articles were made by insane people. all i can say is, to keep using generated passwords and offline 2fa codes. dont click on the naked lady in the spam folder.
have a good night, kids.
Let’s just go ahead and add a third, fourth, AND fifth authentication factor so maybe I’ll kill myself first thing every morning
Passkeys are 100% not a trap, but they’ve been fucked over by being allowed to be portable. Now your passkey is only as good as the portable password solution you’re using to store it. They’re meant to be 1:1 computer->service. Then there’s the issue that most of the sites that accept passkeys let you bypass them with passwords or TOTP anyway.
TOTP, however, is REALLY fucked. Even a rudimentary phishing email can get your time-based key, get in and fuck your account over in real time.
Passkeys are extremely phishing-resistant. They are the best thing we have short of a YubiKey at the moment.
Yubikeys are amazing, But they’re not meant to be permanently carried, just used to stitch your securred devices together.
I use hardware keys to connect to my own self-hosted services and login on (some of) my devices. There is no 3rd party involved.
Some of them like NitroKey are even open hardware. I have backup hardware keys.
It’s amazing. I can’t believe it took me so long to rely on them.
So… IMHO if you don’t like (hardware) passkey it’s because you dislike services relying on them, no the keys themselves.
The biggest problem I have with passkeys is big companies aren’t implementing them to improve your security - they’re implementing them because it absolves them of liability and responsibility for implementing good security on THEIR end and allows them to implement whatever the fuck vibe-coded bullshit nonsense they want without any knowledgeable or skilled staff, and even if it’s good for me too, I’m not inclined to do these assholes any favors. It’ll just make them sloppier and lazier on other elements of security and they’ll turn around and put the blame on the user, and courts will go right along with it because nobody in the legal system can find their asses with both hands.
Using established and tested security implementations instead of rolling your own has been considered good practice since forever. It’s not a bad thing.
It’s not about the implementation - it’s about what passkeys do and don’t do.
Passkeys prevent someone from stealing hashed passwords from the SERVER, but if the server is already compromised badly enough to let someone in, all of the data stored on that server is compromised already anyway. Companies want to use passkeys because there is less involved in implementing secure login credentials, but that is only ONE tiny part of overall end to end security, and I do not for a SECOND believe that they are going to keep on highly skilled, security-minded developers at real salaries when the C-suite says “We’re using passkeys. We’re secure. Fire the high priced developers and get me some interns who can use Claude.”
TLDR: Passkeys are not a magic bullet and they aren’t a game changer, and the false sense of security they push is dangerous.
I realy dont think that’s a thing. End-user login security is a tiny footnote on page 729 of the 2000+ page security document of a large company’s cyber security department. Switching that to passkeys will not change anything about how the company handles security. AI will. But not passkeys.
And as we have seen many times, companies have been bad with security already and many password databases have been breached. Having a tool that limits the impact of bad security is a good thing.
Let’s get back to after 10 years because this was the same debate about drm in browsers.
FWIW I don’t have DRM enabled and I can don’t even remember what part of the Web I can’t browse.
Before you ask, no I don’t use Netflix, or Disney+ or audio streaming service nor do I plan nor want to.
When you use librewolf it pops up when websites try to access drm, ex. finance.yahoo.com wants to access it. It’s not streaming services but lots of news webistes that also serve video.
Right, I’ve also seen warnings too from time to time and yet I didn’t seem to miss enough content to even notice.
Passwords are protected (for now) by the first amendment. You can’t be compelled to tell what it is. Passkeys can be seized with a warrant. This only matters in the US but it does matter and I literally never see that addressed.
That’s not really a bash on passkeys so much as it is a bash on storage methods. Anything with a password that is not no knowledge encrypted is at the exact same risk because the password doesn’t matter to the company the warrant is issued to.
Edit: You may be right about that. I spoke too soon.
Fourth amendment protects against unreasonable search and seizure. That applies to passkeys. First amendment protects speech, that’s what protects your password. You can’t be compelled to tell that because you can’t be compelled to say things, not because there’s any protection against the data being seized. IANAL, feel free to go into more detail if you still disagree
First time I am reading people orate their passwords🤣😂🤣😂🤣
Now you’re going to tell me the US has free press🤣😂🤣😂🤣🤣😂
After reading both of the posts, I’m kind of back where I started with passkeys: neutral. I’m pretty happy with my current setup of a self-hosted password manager, diceware master passphrase and strong, unique passwords for every account, along with an open source app for TOTP. I only ever see passkeys pushed on me for work-related accounts anyway, but I’m not using them there either. I do have a question though if someone can answer: are passkey protected logins also vulnerable to stolen session cookies?
are passkey protected logins also vulnerable to stolen session cookies?
Yes. 100% unchanged.
So it’s fair that you are neutral about them for your own use, clearly you know what you’re doing. It doesn’t make sense to be neutral about them, generally. On usability alone they are not good. There are so many people who don’t have a clue how they work, or their consequences, and just click okay when continually harassed into using them. Some will even go ahead and save one on a shared computers, or someone else’s, ‘because the website says so’.
Honestly, I don’t understand them well enough to recommend them either. I do IT, and I set my users up with a (managed) password manager and MS Authenticator. If I encounter a situation where a user has ended up with a passkey for a given service, I just leave it be. On the other hand, if someone is locked out because of a passkey, I reset it and get them set back up with the Authenticator app.
Hmmm, for someone complaining that another post makes logical leaps, this one has a pretty glaring contradiction that severely undermines their own argument:
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!)
In other words, “attestation is bad and everyone is against it, but it’s a feature of the standard.” What they are really claiming is that there is something that for now is stopping governments and corporations from pushing attestation, but how long will that hold? I didn’t have a horse in this race when I first started reading these posts, but this counter-argument is flawed and it makes me lean toward the camp against passkeys.
It reminds me of when Netflix was big and I told everyone they’d have commercials eventually. Sure you can still buy a plan without commercials, but I suspect that eventually, when money gets really tight for them, will go away.
Same thing here. Right now passkeys are “open”, but who is to say my bank won’t require a Apple/Google managed passkey in the future. Hell, I can’t run the bank app without running a Apple/Google approved apk.
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.
The web wasn’t supposed to be controlled by corps either, and look where we are now.
If passkeys were to follow the same path as the web, here’s what it would look like. Corporate passkeys get the most users because of OS integration and convenience. Now that they have all the users they can commandeer the standards, and make them so complex and evolve so quickly that non-corporate implementations can’t keep up (think Firefox vs Chrome). Corporations convince websites to drop support for outdated passkeys, citing security issues. Non-corporate implementations are locked out. Monopoly is established.
And now that passkeys are centralized to corps, the government can exert power on them, mandating hardware attestation for things like hardware-backed id and age verification. They push for backdoors, so they can log into anybody’s account. Bye bye privacy.
Question: Why did these corps implement TOTP? You should be able to answer this from an economic perspective of them trying to save money.
Another question: why aren’t these corporations locking down TOTP to restrict them to their own validator apps, in the same way you’re proposing that they might do for passkeys?
Why did these corps implement TOTP?
To reduce support load from people getting their accounts hacked and asking support to get them re-instated. I don’t doubt that these incentives also drive the push for passkeys, but passkeys are much more opaque and tightly integrated with the OS, and is thus more vulnerable to centralization.
why aren’t these corporations locking down TOTP to restrict them to their own validator apps
They are. Authy is the biggest offender I know.
Edit: some info about how Authy locks you in: https://www.bentasker.co.uk/posts/blog/general/switching-to-aegis-for-totp-codes.html. Note that some websites integrate directly with Authy and force you to use Authy to set up the TOTP. The only way out is to use a rooted phone to transfer the codes to another app like Aegis.
I don’t doubt that these incentives also drive the push for passkeys, but passkeys are much more opaque and tightly integrated with the OS, and is thus more vulnerable to centralization.
I’m not sure what you mean by integrated into the OS. I use a FOSS password manager on android (keepassdx), storing passkeys both for apps and websites. When the browser or an app asks for a passkey, android uses the password filling service you’ve chosen (in my case keepass), and it loads up, no differently from when there’s a password prompt. I’m not sure how it works on other platforms like iOS, windows, or linux, but at least on android, you can use a FOSS password manager not integrated into the OS.
They are. Authy is the biggest offender I know.
Specific sites aren’t locking down TOTP, this seems to be an EEE scheme of Authy specifically, since as you say the TOTP codes provided by sites still work with other authenticators. I’m referring to the case where say, amazon forces you to use their app to login, or creates their own custom TOTP or passkey app, and won’t let you log into their site without it, and then you have no control over your login method or codes.
why aren’t these corporations locking down TOTP to restrict them to their own validator apps
But they do. There are TOTP implementations that have been intentionally modified to prevent using standard apps. I don’t remember other examples right now, but I think Steam Guard is one.
I’m sure a lot of people (like myself) would refuse to install a special custom TOTP app just to be able to use one site. They’re only hurting TOTP adoption by doing that, and thus increasing the amount of support resources they need to allocate to account hacking / hijacking.
I’m sure there are other companies too willing to go against their economic interests for various reasons, but they’re going to be in the minority.
what makes passkeys any different from all the other times they have embrace, extend, extinguished? what, fundamentally, stops them from using attestation in the exact way the user described? specifically, what stops the following scenario from playing out?
- passkey support becomes commonplace across the web
- many websites stop using passwords due to their inherent security issues
- most users (for brevity, say 90% or more) just use their OS to store passkeys because it’s easier
- apple provides attestation for passkeys stored in the Secure Enclave
- google provides attestation for whatever their business goals are
- google refuses passkeys that aren’t attested due to their “security issues”
- apple does the same, which has the added benefit of killing devices without a Secure Enclave
- maybe PCI-DSS requires attested passkeys because of “security issues”
- maybe financial institutions require attestation (similar to the ctsProfileMatch issue with GrapheneOS)
- 90% or more of users don’t notice or care about steps 4-9
- most of the 10% or less need to use at least one account that requires such an attested passkey
- idk what happens with firefox but i’m sure many firefox users (including me) have encountered a website that could work with firefox but chooses not to (based on User-Agent or similar)
obviously that isn’t the only scenario one could envision but i don’t really see what makes this one unreasonable to expect
Once you can correctly answer the question you responded to, you’ll see why its against their material interests to EEE logins, whether its TOTP or passkeys.
well idk about you but i have the steam guard app on my phone, and it’s a pain in the ass too so it’s not that. plus, unlike TOTP, passkeys are dead simple and integrated into the OS. so i can honestly say i have no idea what you’re getting at and why it applies to passkeys as well as it applies to TOTP.
Sounds like something BigPassKey would say
But they are annoying. Like it’s fine if you only use one device, but I don’t fucking know where my phone is, that’s why I am on my laptop
Agreed, but it can be better, with open solutions.
If you use a popular open source OTP solution (like Aegis), you can export your tokens (carefully) as an encrypted file from your phone, and then import them to another popular open OTP solution on the laptop.
Alternately, one can also set up each separate device as a separate authorized token for each service - for many services.
I like the import/export solution, because even for services dumb enough to only allow “one token”, I can still have that token on two or more devices.
Not much of a rebuttal imho. We still have the problem that passkeys are ok in theory, but in practice they’re being pushed as a way to increase lock-in and don’t offer compelling advantages over well-managed passwords.
But most people don’t have well managed passwords. And me having good password hygiene doesn’t stop my data being hacked when someone working at a subcontracting firm to a company I use leaks all my data.
It also is annoying to have to log in over many steps with 2fa, often forced to email or SMS.
Collectively improving security benefits us all.
I think the point about lusers not being able to manage passwords has been argued to death elsewhere, so I won’t take issue with that.
me having good password hygiene doesn’t stop my data being hacked when someone working at a subcontracting firm to a company I use leaks all my data
What has this to do with passkeys? Are you sending your password in plaintext to the contractor who stores it that way, unencrypted? That’s a separate problem entirely. The only benefit I see with just sending them your public key is that they can’t leak your private key, whereas if you used one password for everything, and sent it to them, they could leak it.
Am I missing something? Would passkeys offer an advantage over a password manager? What if the website assigns you a password via DH so that users can’t pick bad ones or reuse them, would it have the same advantages?
2FA can be super annoying, but again I think it’s a separate issue. If I get control of your phone or laptop then 2FA might save you, but passkeys won’t.
It sounds like they’re saying that if you can manage your passwords then do so yourself and avoid passkeys, but if you can’t/don’t want to then use passkeys.
And they are pointing out that the company is far more likely to lose your password than you are.
Convenience vs security, but the weakest link is probably not the user.
I think you’re mixing up compromise of an account with compromise of the data associated with that account.
If a particular piece of data is accessible to people of a dozen accounts, compromise of any of those accounts potentially compromises the data. That’s a legitimate concern for people who want certain data secured, whether other accounts with access are also secure. In some cases, it may be best to have an authentication policy that provides a baseline level of protection even for the most clueless users, rather than a system where you’re able to secure your own account.
I follow you, but if we can impose passkeys on the security-inept people we are forced to give our sensitive data to, couldn’t we instead force them to use good security?
It’s been like 25 years since the security world basically moved on from assuming that users could be trusted to act securely. We gotta design processes and protocols that keep things secure even with people who have bad habits.
I can secure my email, but every email I send or receive touches at least one other mailbox I don’t control, of some other user. Same with text messages, social media posts, etc. The digital world we use has a billion overlapping people, some with escalated privileges as employees or admins or mods or whatever. We can’t make them perfect, so we should design systems that work well even with imperfect people.
I couldn’t possibly argue with that
I’m saying that bad user passwords allow data to be hacked. When it’s the credentials of someone with access, like an employee of companies with your data, then that data is more easily compromised if they have crappy passwords. It’s harder to compromise with passkeys. It is not just your password hygiene that protects your data.
Here is a recent example in Australia. https://www.abc.net.au/news/2026-10-06/asos-app-users-sent-hacked-message/107236520
That doesn’t say anything about passwords. Looks like someone’s device was accessed. Maybe you just understand this better than I do.
Ok, here’s another one from Netherlands. https://www.tomshardware.com/tech-industry/cyber-security/hacker-claims-123456-password-let-them-breach-the-danish-national-registry-accessing-8-8-million-records-it-and-data-services-company-with-weak-passwords-linked-source-of-the-hack
If the people with access to your data have weak passwords, then so do you.
but in practice they’re being pushed as a way to increase lock-in
Which ones are doing this? Give specific examples of sites that are forcing you to use a specific TOTP or passkey validator.
The kind of lock in I’m thinking of is with e.g. Google, Apple, or Microsoft when they take charge of the passkeys for you.
That’s entirely optional and not forced. You can use FOSS password managers that store your passkeys, that can log into all those services.
If you’re referring to proprietary password managers (IE like google or apples), then that concern applies equally to all the passwords you’re storing with them. So that concern is not specific to passkeys.
I don’t disagree with any of that. You and I will be fine, as long as whatever sites we use don’t insist on evil-only providers. The trouble I’m thinking of is for average uncritical phone enjoyers who are guided into a flow where they’re migrated to using passkeys with whatever propriety junk they’re using and end up locked into Matacorp Secure Cloud who now control their access to all their accounts, where once they had a list of passwords written in the back page of their diary.
But that’s exactly the problem. Those that were the target audience for the article do not have well managed passwords. For them the passkeys arguably do increase security, while having a bit more “lock-in”.
For those that have well managed passwords (like probably most in this community), they are perfectly fine to use because they don’t have lock-in either. I have full control over my used passkeys.
Basically you’re not getting the “normies” to use proper password management, and for them they do provide additional security and convenience. They can always add more passkeys on different vendors, you’re not limited to just 1 per service. Yes, adding them is a hassle, but so it’s managing passwords and following higher security standards in general.
The “normies” don’t have a clue what passkeys are either.
They don’t need to. It just works to log them in when they’re using one of their own trusted devices. Being able to unlock their phone gives them full access to the services (apps, websites) that are authenticated to that device.
I know that, and you know that, but passkeys are supposed to solve security-related problems by reducing friction.
What passkeys can’t overcome is people dismissing the popups asking if they want to switch to passkeys or create them.
The problem with passkeys is they are 20 years too late, and no one cares.
What passkeys can’t overcome is people dismissing the popups asking if they want to switch to passkeys or create them.
I think it’d actually be pretty easy. Just ask:
Trust this device, with biometrics?
Most people will say yes on their Apple/Samsung/Google devices.
How do they increase lock in?
a way to increase lock-in
Lock-in was already being achieved by mandatory use of apps which require iOS or Google Play services.
Plenty of banks etc which I can simply not use because of this requirement, and others which downgrade you to password+SMS security (used to be a physical TOTP token) if you refuse their app.
This was on hackernews this morning.
The author is in the passkey business.
The most pertinent question there imho was : What do passkeys offer that random strong passwords + a pw manager do not?
There was a wall of comments, but no concise answer.
======== You buy a new super secure lock for your house, but to get in you go to one of the 3 conveniently located HomeDepot’s in your city. You simply prove your identity to the guy there. He verifies you in the system. Then he gives you a one time pass to your house.
If its such a great idea, you can pay me now to do it for your home.
The way i understand it, passkeys test for a combination of what you have and what you are (for those that check user presence, which is all of them I suppose); whereas passwords test what you know.
From my reading, passkeys give more control to the platform/service provider, whereas passwords do the reverse.
The former clearly benefits corps in their unique ways - motivated by profit, security, data/spying and so on.
The current iteration of passkeys is not the form that is being challenged by the earlier anti-passkey post. But rather a floodgates problem. Pretending that it will never happen is asking for trouble.
The better option (be it passwords or passkeys) needs to demonstrate that it gives control to the user.
I’m in the passwords camp, I do not see what convenience or added security passkeys might provide in any of my use cases that is worth sacrificing my level of control and choice.
