1

I'm currently using two-factor between my Mac and iPhone. And I also use it for my Google account. (Those are the two only ones at the moment.)

How I can protect access to my accounts if I don't have a mobile phone?

  1. First, I'd like to understand if two-factor on a mobile phone is stronger than using a two-factor method that does not involve a mobile phone? If so, what particularly about a mobile phone makes it more secure? Is it because mobile phones have SIM cards, and no-one can get a SIM card without signing up with full name with a phone carrier, etc.?

  2. What alternatives do I have for two-factor for Apple ID / Gmail that does not involve a mobile phone? (Preferably something that does not require obtaining a physical item or signing up for some paid service.) Can sending a token by encrypted email be used, for example?

forthrin
  • 1,821
  • 1
  • 14
  • 22
  • 1
    SMS as a second factor is not recommended. Would you consider a two-factor app on a phone that has no SIM? I do that with an old phone. It's just an authentication device. – schroeder May 24 '17 at 13:28
  • "two-factor" as you use it in your first point is very broad - what do you mean by the term? An app? An SMS code? – schroeder May 24 '17 at 13:29
  • Maybe I've got the terms mixed up. But by "two factor", I mean that it's impossible to log in to an account only using a password. You have to somehow get a one-time code from another device or account, thereby increasing the security. The question is how I can achieve this without a phone at all. (And understanding where specifically the strength lies in the device we know as a mobile phone.) – forthrin May 24 '17 at 13:39
  • ok - you're using the term correctly - did you know that you can use a non-phone iPod app as a 2FA code generator? – schroeder May 24 '17 at 13:51

2 Answers2

1

Relying on anything controlled by a mobile carrier is a bad idea. SMS is insecure by design (it transits in plain text) and mobile carriers don't care about security unless it interferes with their ability to scam their customers, so they couldn't care less if there's a bad guy pwning their infrastructure and intercepting 2FA texts en masse (given the horrors I've seen at a major UK carrier I wouldn't be surprised if most carriers already have advanced malware planted somewhere deep in their infrastructure).

For email you could set up your own fake "email" server that responds to email queries (with the site's name) and responds with the corresponding 2FA code. Internally that server would be mimicking the functionality of the "authenticator" apps (TOTP/HOTP are open standards and the online services don't know nor care whether you're using a smartphone app or some obscure solution like this one). You'd be connecting to the email server securely and you'd have some scripts that interpret incoming email queries and putting the responses (with the codes) directly in its "inbox" IMAP folder for your email client to pick up.

André Borie
  • 12,826
  • 3
  • 42
  • 76
  • According to this article, intercepting SMS is not straight forward. https://security.stackexchange.com/questions/11493/how-hard-is-it-to-intercept-sms-two-factor-authentication – forthrin May 24 '17 at 18:23
  • Making a fake email server sounds like quite a low level job. Is there some ready-to-use software for this? 2. And how would you make Google/Apple talk to your fake email server in the first place?
  • – forthrin May 24 '17 at 18:25
  • @forthrin "How is data secured within the provider's network, and between the provider and the server which wants the SMS to be sent, is out of scope of the GSM specification" so yeah. The other (very good answer) focuses on data transiting between the phone and GSM tower while my answer is about the bigger picture, including the network equipment at the provider and their business policies which prioritise scamming over security. – André Borie May 24 '17 at 19:42