4 ms·
>we actually know very little about how well two-factor authentication works Actually we have known literally for years, maybe over a decade, that SMS-based tw
by jchw 8y ago
>we actually know very little about how well two-factor authentication works
Actually we have known literally for years, maybe over a decade, that SMS-based two factor is insecure and prone to phishing... that's the point of TOTP/shared secret based two-factor auth...
- jacoblambda 8y agoI think the point of the article was to spook the non tech crowd into moving away from SMS based 2FA. Obviously the tech crowd has known for a long time but most other people are oblivious to all of this.
- jchw 8y agoReally? They mention YubiKey but it seemed to me like they just lumped it in with less effective SMS 2FA.
- sgustard 8y ago> Obviously the tech crowd has known for a long time Who else but the "tech crowd" implements SMS 2FA on these websites? What does it say about our industry if we're pushing solutions we know to be flawed?
- scrollaway 8y agoIt's not about who implements it, it's about who pays to implement it and gives the orders. The tech crowd isn't implementing SMS 2FA for fun. They're doing so because the manager is like "wait what! they'd need to install an app? but we can just use SMS! I don't care what you say about it being insecure, it's still more secure than not having it!" What's the fix? I mean for fucks sake, naming & shaming companies doesn't ever work for security stuff. It doesn't even work for getting https on login forms; it's not like it's easy to push through the nuances of SMS 2FA's security issues. Or even tech stuff in general. I just moved to Belgium and half the national services here don't know how to dial an international phone number, don't support + or 00 at the beginning of phone number inputs, etc. There is no end to how technologically illiterate services can be. And yet, it's still "the tech crowd" implementing all these things. We need to find a way to push these obvious fixes through, but as far as I know, short of reporting the issue and crossing your fingers someone relevant hears it, it's not possible.
- rebuilder 8y agoFixing it seems like a tough task. At first glance, somehow requiring tech vendors to work not to fulfill the customer's technical specs, but their actual real-world needs, seems necessary. But all other problems aside, if the customer doesn't have the knowhow to specify their needs in the first place, that's a tough task. Maybe it would have to be a combination of bolstering the buyer side's in-house technical understanding and legally requiring providers to commit to delivering the product their customer needs, not the one they say they want. I wouldn't want to try to formulate that into concrete legislation, though. It would be an enormous change, and I'm not sure what we'd end up with if we tried that.
- cwyers 8y agoThe "tech crowd" tends to implement what the business asks them to implement, like you said. In the case of security, fixing it is straightforward -- there's a large enough amount of fines for breaches where customer data was leaked to a third party where any company would either implement really good security or hire out to platforms that could do it. It's not easy, because there's not a lot of people in government who have incentives to make that happen.
- gsich 8y agoStill better then nothing.
- Phlarp 8y agoIs it not possible to capture both the login credentials and TOTP code from a phishing form and submit them to the real service in real time? It would seem push notification style 2FA ala icloud/gmail/Duo/blizzard is the better solution but that also opens up a vector for users who simply accept every push notification request. U2F would seem better than both those options but alas that can still be lost or stolen and compromised before access can be revoked.
- deleted 8y ago[deleted]
- m-p-3 8y agoThis is why having two tokens (one primary you carry with you and one backup kept in a secure location) is important.
- altmind 8y agoNot only SMS-based two-factor is susceptible to phishing, its also susceptible to intercept/forging by the rogue governments (RU) https://meduza.io/news/2016/04/29/mts-otklyuchil-oppozitsioneram-sms-servis-vo-vremya-vzloma-ih-telegram https://meduza.io/news/2016/04/29/mts-otklyuchil-oppozitsion... And very limited security in SS-7 makes it possible to hijack the messages even for the foreign phone numbers. (Edit) Just to point our, here I talk not about possibility of sms interception - I'm talking about sms intercept that DID happen in 2016 and is widely publicised and have a lot of sources, including timeline of this event and comm with the mobile service provider(albeit, this info is mostly in russian)
- panarky 8y agoIt's not just SMS that's vulnerable. 2fa apps like Authy are also at risk from fraudulent interstitial sites that capture your user ID, password and Authy code, authenticate with the legitimate site, and allow the fraudster to control your account. Really the only secure 2fa is a hardware token.
- hn_throwaway_99 8y agoWhile hardware tokens are definitely more secure, there is a large difference between the security of SMS 2FA and TOTP code-based 2FA. SMS 2FA is fundamentally insecure because the SMS system can be hacked regardless of the security consciousness of the end user. On the other hand, while TOTP code-based 2FA is certainly subject to phishing, there are 100% effective ways that an end user can prevent this (like double checking the URL). So while I do agree with you that hardware tokens are best, it's a mistake to lump SMS in with other forms of 2FA from a vulnerability perspective.
- tptacek 8y agoNo, I don't think this is true. TOTP 2FA has the advantage that your 2FA codes can't be stolen by porting your phone to another device (an attack teenagers can pull off), and, in elaborate attack scenarios, TOTP also has the advantage that it's not susceptible to attacks on SMS itself. But both TOTP and SMS are phishable, and moving from SMS to TOTP is not a meaningful anti-phishing defense. U2F and Webauthn resist phishing using a form a mutual authentication, which is why security keys actually do resist phishing, and why Google switched to them and away from TOTP.
- hn_throwaway_99 8y agoI think you misread my post. I wrote "while TOTP code-based 2FA is certainly subject to phishing..." My point being that at least with phishing attacks the end user can prevent them by paying attention. With SMS 2FA, even if the end user does everything right they are still open to getting hacked. For example, a bunch of people had their Bitcoin stolen when bad guys convinced the phone company to change number ownership.
- yalogin 8y agoHow is the other method supposed to help? The secret is generated completely on the client dongle and so if phished the attacker is going to get the token needed for that time window. The attacker logs in and disables the 2FA.
- tptacek 8y agoTOTP 2FA is also susceptible to phishing.
- mbesto 8y agoSusceptible, but more limited. I think an article should be written like this: "There isn't a security measure that exists short of locking a computer in room with a keyless door and no external connection that is completely flawless to hacking, there are just varying degrees of computer security and 2FA happens to be safer than others".
- UncleMeat 8y agoHow more limited? In both cases you type some numbers into a form field. The phishing attack is exactly the same.
- mbesto 8y agoPhone number vulnerabilities include the unique vectors of: - Someone porting away your phone number from your wireless provider - The ease of confusion of a txt message asking you to send a generated OTP (e.g. you're more likely to forward a OTP generated from a SMS to another SMS, than you would from a TOTP generator) - Wireless provider can theoretically read the message in transit (or backdoor code, whether from a gov't agency or a malicious actor acting on behalf of the wireless provider) Those are just 3 I can think of off the top of my head...I'm sure there are more.
- akerl_ 8y agoThe first and last of those aren’t phishing, and the middle doesn’t seem likely. I’ve never legitimately been asked to text the code I just got via text
- Buge 8y agoTOTP is just as vulnerable to phishing as SMS. If you want phishing protection, use U2F.
- jchw 8y agoYes that's true actually, it's U2F that actually fights phishing directly. I use TOTP integrated into my password manager, so it does partly fight phishing in that sense, since I can't accidentally enter it on the wrong domain. Though it is still worth considering SMS insecure due to the many other pitfalls that aren't phishing, where TOTP fairs a bit better. Still, I wish more stuff supported U2F.
- Buge 8y agoWhat password manager do you use that uses TOTP?
- jchw 8y ago1Password and Bitwarden support TOTP. Obviously, you lose the security of having two separate factors to compromise, but you gain the normal mechanical advantages of TOTP and a bit of extra phishing protection. I have a few YubiKeys as well, but yeah, less stuff supports that...
- Tepix 8y agoBesides the other two mentioned there's also Codebook.
- cyphar 8y agoKeePassXC supports TOTP, though it's still manual copy-paste (while the browser extension checks websites, and requests access from your KeePassXC session it doesn't support entering TOTP so you have to do it manually).
- amanzi 8y agoIsn't TOTP also prone to phishing? If I can present a form to someone and trick them into entering their credentials, why not present a second form that also requests the TOTP code? That gives me a window of opportunity to log in as the user, or just script that part of it to happen automatically. Would that not work?