SandbagTiara2816@lemmy.dbzer0.com to Technology@lemmy.worldEnglish · 4 months agoAuthy got hacked, and 33 million user phone numbers were stolenappleinsider.comexternal-linkmessage-square147fedilinkarrow-up1716arrow-down16cross-posted to: selfhosted@lemmit.onlinelinustechtips@lemmit.onlinetechnology@lemmit.online
arrow-up1710arrow-down1external-linkAuthy got hacked, and 33 million user phone numbers were stolenappleinsider.comSandbagTiara2816@lemmy.dbzer0.com to Technology@lemmy.worldEnglish · 4 months agomessage-square147fedilinkcross-posted to: selfhosted@lemmit.onlinelinustechtips@lemmit.onlinetechnology@lemmit.online
minus-squarecanadaduane@lemmy.calinkfedilinkEnglisharrow-up19·edit-24 months agoOn Android, I replaced Authy with the open-source Aegis app. It’s just as functional, allows exporting, and doesn’t tie your data to your phone number (nor store it on a central system–not sure if Authy does this or not).
minus-squareContravariant@lemmy.worldlinkfedilinkEnglisharrow-up11·4 months agoUse TOTP wherever possible. It’s standardized, and typically can be found somewhere if you keep digging hard enough. Plenty of services push their own proprietary systems hard though. Looking at you M$
minus-squareTryptaminev@lemm.eelinkfedilinkEnglisharrow-up3·4 months agoI also find this infuriating. I had a service offer TOTP for authentication. Installed an open source TOTP Aap, scanned the QR and voila. The service meanwhile can control whether they want to generate a new token or give out the old one again, for instance when a device was lost. It is the most easy, most convenient solution both for the service provider and the client. There is no excuse for any other 2FA system to be used.
So what did you do?
On Android, I replaced Authy with the open-source Aegis app. It’s just as functional, allows exporting, and doesn’t tie your data to your phone number (nor store it on a central system–not sure if Authy does this or not).
Use TOTP wherever possible. It’s standardized, and typically can be found somewhere if you keep digging hard enough.
Plenty of services push their own proprietary systems hard though. Looking at you M$
I also find this infuriating. I had a service offer TOTP for authentication. Installed an open source TOTP Aap, scanned the QR and voila.
The service meanwhile can control whether they want to generate a new token or give out the old one again, for instance when a device was lost.
It is the most easy, most convenient solution both for the service provider and the client. There is no excuse for any other 2FA system to be used.