5 ms·
OK, so here are the options I've seen people deploy for 2FA: 1. Force users to register two U2F tokens. Google's 'advanced protection' requires this. 2. Have
by michaelt 8y ago
OK, so here are the options I've seen people deploy for 2FA:
1. Force users to register two U2F tokens. Google's 'advanced protection' requires this.
2. Have users print out one-time-use recovery codes and put them somewhere safe. This is what Google does without 'advanced protection'.
3. Require the user to provide a cell phone number, thus offloading the problem to cell phone companies, introducing all the insecurities that result from that. This is what Apple does (as far as I can tell)
4. AWS is similar, but requires both an e-mail and an automated phone call.
5. Github delegates 2FA recovery to Facebook, via their "Recover Accounts Elsewhere"
6. Facebook allows the user to designate 'trusted contacts' who can get a code they can give to the user in person or over the phone.
7. Have the customer contact customer services, who follow a process companies are cagey about disclosing.
8. In corporate settings, just have them visit helpdesk in person.
- ehsankia 8y agoI like #2 the best personally, though #6 sounds interesting too. For something like #5, let's hope the other website's auth isn't on the same key too :)
- mrhappyunhappy 8y ago#2 sounds most appealing. I live in Japan and don’t have a reachable phone #. Wife and I simply FaceTime if we need anything. Otherwise I have no mobile means of authentication. There have been several occasions where I simply couldn’t use the service because I could not authenticate via a phone number. I feel that companies that force this method of authentication have never considered my use case and could care less if they lose me in the signup process. Too bad. I for one actually have the money to pay them, but hey, if you don’t want it that’s fine with me.