Re:What’s in a PR statement: LastPass breach explained
by isthisthingon99 on Tuesday December 27, 2022 @01:01PM
(#34151524)
Since i use Google Authenticator for numerous services this is going to happen to me one day. So what I did was set it up on more than one phone.
[ Parent
| on HN ]
Re:What’s in a PR statement: LastPass breach explained
by mdaniel on Tuesday December 27, 2022 @01:14PM
(#34151700)
I would legit pay money for Google to pull that piece of junk from the Play Store, because it's damn malpractice at this point, given there are so many other options that don't straight-up swallow the TOTP keys
Re:What’s in a PR statement: LastPass breach explained
by isthisthingon99 on Tuesday December 27, 2022 @01:21PM
(#34151796)
Sorry what
Re:What’s in a PR statement: LastPass breach explained
by ThrowawayTestr on Tuesday December 27, 2022 @01:44PM
(#34152102)
I also have two phones with Google Authenticator. Is that a bad idea?
Re:What’s in a PR statement: LastPass breach explained
by FreakLegion on Tuesday December 27, 2022 @01:48PM
(#34152173)
You can back the secrets up to a text file, print them out, etc. too. They're short Base32 strings and TOTP is a standardized protocol with an RFC (6238) and everything.
Re:What’s in a PR statement: LastPass breach explained
by isthisthingon99 on Tuesday December 27, 2022 @04:11PM
(#34153863)
Yes i did this too
Re:What’s in a PR statement: LastPass breach explained
by jve on Wednesday December 28, 2022 @09:04AM
(#34161033)
Except it is cumbersome to doo on Google Authenticator. You must press export to get shown a giant QR code. You can't screenshot it. Must photo with different phone and print on a piece of paper for offline storage.