5 ms·
Google will add E2E encryption to Authenticator backups
- gnabgib 4y agoRelated discussion yesterday: Authenticator cloud sync: Google can see the secrets, even while stored (378 points, 126 comments) which is from the Mastadon version of the twitter post quoted. https://news.ycombinator.com/item?id=35708869 https://news.ycombinator.com/item?id=35708869
- ortusdux 4y agoAlso - Google Authenticator now supports Google Account synchronization - from 2 days ago (464p,325c) : https://news.ycombinator.com/item?id=35690398 https://news.ycombinator.com/item?id=35690398
- jordigh 4y agoI wonder how long until "Mastadon" becomes an accepted spelling, just like "imposter" seems to have replaced "impostor" over the last few years. English schwas are killer.
- judge2020 4y agoIt's been a misspelling for a while it seems https://books.google.com/ngrams/graph?content=impostor%2Cimposter&year_start=1800&year_end=2019&corpus=en-2019&smoothing=1&case_insensitive=true https://books.google.com/ngrams/graph?content=impostor%2Cimp...
- masto 4y agoI wouldn't mind getting my name back.
- jacooper 4y agoWell that was quick
- great_psy 4y agoIt would be nice if a company did the right thing by themselves, not only when the angry mob shows up.
- coding123 4y agoI agree though, it was quick. It seems like most of the time when there's some kind of outrage (at least on HN) there's just silence for 20 - 40 days, then some kind of announcement that either doubles down or backs off. This whole outrage started what, Yesterday?
- pgeorgi 4y agoThat quick response is indicative that E2EE might have been on the roadmap already. It's a bunch of trade-offs: - Keep things as they are - Avoid TOTP data getting lost with lost passwords - Avoid TOTP data getting distributed when the Google-side backup ends up becoming public Maybe this might have been a suitable situation for a "beta" label, though: "We have this, it offers advantages, it has caveats, if you don't care about them, feel free to sign up, otherwise wait until we sorted it out." (Disclosure: work at Google, but no insight into what Authenticator is doing)
- miohtama 4y agoHow the f** they did not have them to begin with? Since when Google has become totally incompetent. They are quite sure that two-factor authenticator is use on security sensitive properties, including Google’s own services. This is like begging Google Drive hackers to get your two-factor seeds.
- miohtama 4y agoHow the f** they did not have them encrypted to begin with? Since when Google has become totally incompetent. They are quite sure that two-factor authenticator is use on security sensitive properties, including Google’s own services. This is like begging Google Drive hackers to get your two-factor seeds.
- 4y ago
- worldsavior 4y agoI thought it exists already. Apparently...not.
- DesiLurker 4y agoyes my thoughts exactly. I guess its best to assume the worst when profit motives are factored in.
- amf12 4y agoLooks like you did not read the linked post.
- ballresin 4y agowill... add?!?
- heipei 4y agoI don't get why anyone would use Google Authenticator over Authy which had device sync, backup and E2E encryption for years.
- mey 4y agoMicrosoft Authenticator has backup options but doesn't indicate if there is encryption which is concerning. https://support.microsoft.com/en-us/account-billing/back-up-and-recover-account-credentials-in-the-authenticator-app-bb939936-7a8d-4e88-bc43-49bc1a700a40 https://support.microsoft.com/en-us/account-billing/back-up-...
- skinkestek 4y agoAlso I burned myself by activating backups in the app and not realizing I had to activate it in system settings in iOS too (or something to that effect). So I lost my 2-factors, luckily I had spares for most.
- jacooper 4y agoHow is authy end to end encrypted?
- nicpottier 4y agoMy understanding is they encrypt your database with a password before syncing to the cloud. They don't sync the password and there's no recovery.
- crazygringo 4y agoBecause they use the Google ecosystem and don't want to deal with yet one more account with yet one more company. Easier to keep things in one place.
- toastal 4y agoDoesn't Authy require a phone number? I don't know why you'd use Authy over something open source.
- ezfe 4y agoSo they didn't have sync for years, presumably because they felt like it was insecure - and when they finally add it, it's not E2E encrypted
- 0xbadcafebee 4y agoIt took them 12 years to add sync, I wonder how long E2EE will take
- wslh 4y agoI think the big picture is that security is winning: Apple also adding U2F, etc. All this implies that we will see more E2E and identities disconnected from our mobile phone numbers, which is great.
- danuker 4y agoAnd maybe those identities will be magically synced to and from central servers, which would not be so great.
- judge2020 4y agoThe option to "sign in with" a third-party provider is already extremely widespread and most people prefer it. But U2F/Fido identities are better in that the people who prefer to ensure their keys are in escrow with a corporate overlord can choose to do that, while security-conscious people can go a step further and use physical security keys or third-party solutions with different sync mechanisms.
- wslh 4y agoSecurity is a nightmare when you trust systems that you shouldn't trust. That's for sure.
- xdennis 4y agoGoing from mobile phone numbers to smartphones is not an improvement. It's just going more expensive and more monopolized. The only improvement is that you don't have to link your account to government photo ID (which is mandatory in many countries to buy a SIM card).
- BiteCode_dev 4y agoWell, until we learn that there is a backdoor in their implementation, allowing any big actor to swoop in and either crack the crypto easily, have access to an unencrypted copy, or steal the passphrase. Then we just have put all the things in the same basket for the convenience of mass spying, like we did with https, which any entity big enough can MITM by using their root certificates.
- jbverschoor 4y agoSounds like damage control wrt the last post. Sorry nope.. privacy, encryption, security is not their thing. Even if they’d have e2ee, it’s just a patch to a bad culture
- crazygringo 4y agoKey quote: > Google Group Product Manager Christiaan Brand told BleepingComputer that due to the possibility of end-to-end encryption causing users to get locked out of their own data, they are rolling out this feature carefully in their products. I know everyone's pro-E2EE here but this rationale should be taken seriously. I absolutely believe E2EE is an important option to have, but it also makes sense for it not to be the default. If you keep all your passwords synced in Chrome, for instance, none of them are behind E2EE either. If you use Gmail, all your password resets will go to your Gmail which also isn't E2EE. If you use Google Voice, SMS login codes will go to that, also not E2EE. It's not like syncing Authenticator data is less secure than anything else, and Google accounts are already awfully secure generally. For most people, adding a new password/key just for Authenticator is just one more thing to forget/lose, especially since it's something they'll probably only touch every couple years. I think it's good to add E2EE as an option, but only for the minority of users for whom the necessity of extra security outweighs the risk of losing access entirely.
- candiddevmike 4y agoUnderneath all the layers of security and encryption and footguns is still almost always a password...
- Someone1234 4y agoWe've invented better things, but they inherently have the problem of: What if I lose/break/etc my hardware token? What if it gets stolen? Plus of course the vendor lock-in potential. The closest we really have is biometrics but even those have complexities, particularly with deep-fake style tech getting really near perefect.
- taeric 4y agoI'd rephrase. Underneath it all is a secret. Classically, passwords were shared secrets with someone. Everything since has come down to a way to not require direct sharing.
- BiteCode_dev 4y ago
- 1attice 4y agoCalling this 'end-to-end encryption' really bothers me, as we already get that from HTTPS. What this ought to be called is 'encrypted-at-rest' (EAR). Words are important; there's an obvious downgrade attack where E2EE is implemented as EAR, but then later watered down to something like HTTPS (where the pipes are encrypted but that data is stored unencrypted.) You could do this without changing the language of the product offering, provided that the product is sold and marketed as 'end-to-end'. Whereas if you created an EAR system and marketed as such, you'd be vulnerable to lawsuits if you pulled a bait-switch (which you might have done because the FBI is leaning on you.)
- Obscurity4340 4y agoDoes encrypted at rest necessarily preclude Google from retaining keys? It seems like the same schtick Apple had for all these years where they said iCloud data was fully encrypted (which was true) in the hopes everyone would conflate "encrypted" (you and them have the keys) and e2ee (where they don't handle the keys).
- 1attice 4y agoGood point.
- jjav 4y ago> Calling this 'end-to-end encryption' really bothers me, as we already get that from HTTPS. You very rarely get end-to-end encryption from HTTPS. It's possible, if the TLS session is actually between the two ultimate end points (the two ends in end-to-end). But that's very rarely the case.
- DueDilligence 4y ago[dead]