Re:On Phone Numbers and Identity
by kalleboo on Wednesday September 28, 2016 @01:27PM
(#12599529)
The best advice for SMS 2FA I've seen was what was given to YouTuber boogie2988 by his attacker after he was hacked the same way - use a separate prepaid phone number that you never make public.
[ Parent
| on HN ]
It doesn't scale as you need to share the number across different services. To be completely decoupled you'd need to have 1 number per account all bundled into one sim card. I don't think this is something you can setup with current services and phone software.
I mean, you could do it with Flowroute or Twilio. I already pay $1.25/mo for a DID for my home from Flowroute, if I cared enough about security buying another isn't going to put a dent in my pocketbook and I could just have a small little flask app somewhere forward them to a prepaid phone.
Or once a company gets hacked, since that will be unencrypted in the users table. eg the linkedin data dump.
Re:On Phone Numbers and Identity
by paulsutter on Wednesday September 28, 2016 @02:47PM
(#12600197)
Be nice to have a special device with sole purpose sms/2fa, that's very small (easier to carry than a spare phone). A secret number of course, but also running on a service with no human operators who can intervene.
Re:On Phone Numbers and Identity
by AstralStorm on Thursday September 29, 2016 @01:34AM
(#12603461)
Good banks issue true tokens or one time random code cards for exactly this purpose.
A token is a device that generates a known set of pseudorandom numbers. These are relatively cheap - and many modern auth systems depend on the token being installed on a much less secure shared hardware, such as a phone. Still harder to crack than SMS.
Re:On Phone Numbers and Identity
by icebraining on Wednesday September 28, 2016 @06:38PM
(#12601926)
A cheap featurephone is pretty small, and you can even run a J2ME TOTP client, besides SMS.