I could see them integrating it into Settings under Passwords & Accounts…along with saving your password for a given site you can scan a QR code and have iOS generate one-time codes that would be generated and suggested above the keyboard, without using SMS, any time a one-time code is requested on the domain(s) associated with that account. It’d be a nice setup, but they’d absolutely be sherlocking Authy, 1Password, et al. I suppose they could also open up an API for those apps to suggest one-time codes, but that’d be risky, I feel like.Indeed, I bet Apple could do it by themselves if they just bundle a 2FA app into iOS using a common open protocol. It's hard to get users to downloading Authy or similar app, but if its built-in it will take off. Service providers will be incentivized to adopt that protocol so their 2FA can be native in iOS, and the Androids will copy Apple as they always do.
I think that some of the services I have used intentionally make the message long so that the code won't show up in the notification on most phones.
That way, the device has to be unlocked to read the code.
There is also often an element of warning people about scams.
I feel like Apple's proposal assumes that you want to use the code on the phone itself, and in my experience, that's rarely the case.
Agreed. It's also meant to work on MacOS (assuming one has text forwarding on) but it's never worked for me. I get the sms forwarded to my Mac, but Safari ignores it.The way iOS captures the text code and fills it automatically is so convenient. It’s one of those little features that just makes things a bit easier and I smile every time it does it.
But, if we are pushing people to unsafe options, then we are doing them a disservice. The fact that this still uses SMS as a delivery mechanism makes it less safe than other methods.
To me, I always want to use the safest option. In order:
1) Hardware Key (which is rare)
2) Soft/Hardware Key - Approval requests are sent to an app on my phone and I have to approve them there. (Best apps are ones that allow approval directly from the notification after I authenticate.)
3) TOTP - 1 Password makes using TOTP so much easier.
4) SMS - Better than nothing, but becoming less safe these days.
5) Nothing.
Way to solve the problems of 10 years ago. Apple used to be more forward looking than this.
In 2020 sites should be using and supporting TOTP codes like those provided by Authy or even better Yubikeys and the like. SMS two-factor is vulnerable to mobile provider compromise, and these attacks have occurred in the wild for high value targets like crypto wallets.
I agree. They could also use the secure enclave chips on their devices to hold the TOTP keys (similar to Yubikey Authenticator). Actually, Apple already has an offline TOTP generator in iOS and MacOS ("get verification code"), but it's only usable for iCloud logins at the moment ...2FA using SMS is better than nothing, but is not very secure because of how SMSs can be intercepted.
If Apple is pushing for standards, why not standardize a proper 2FA protocol (e.g., OATH) and require all smartphones to have a standard compatible authenticator app built-in?
Indeed, I bet Apple could do it by themselves if they just bundle a 2FA app into iOS using a common open protocol. It's hard to get users to downloading Authy or similar app, but if its built-in it will take off. Service providers will be incentivized to adopt that protocol so their 2FA can be native in iOS, and the Androids will copy Apple as they always do.
exactly! SMS 2FA needs to go away.Doing 2FA by sms can be “hack” with SIM Swapping, so I don’t think it is a secure way to do this.
The one similar that bugs me to now end is with Apple themselves. I'm trying to do something with Apple on my iPhone, and it sends me a 2FA code on the iPhone I am trying to get in on. Why can't it transfer the code like with other messages since I can't keep the code on my screen and enter it. I need to remember and quick enter it before I forget.Yes please! I hate it when making a payment, your bank sends the text but you can only copy the entire message as a whole so you have to remember it. And the code expires after a few seconds.
Actually, not being able to select and copy text from messages is extremely annoying, like when someone sends you someones phone number or email address but doesn't leave a space before and after it... The bane of my existence.
2FA using SMS is better than nothing, but is not very secure because of how SMSs can be intercepted.
If Apple is pushing for standards, why not standardize a proper 2FA protocol (e.g., OATH) and require all smartphones to have a standard compatible authenticator app built-in?
I agree this is an issue, but it's solvable.The problem is when you build a site for the public, you realize that you can't replace SMS. SMS is identity-based, specifically, you get access to your phone number based on (hopefully) the carrier checking your government-issued ID. That doesn't hold for a token or authenticator.
Consider the case somebody loses their phone. What if they keep their USB token in their purse and it gets stolen? What if their house burns down?
A security person is going to say that they should print a recovery code and lock it up, but you know when you ask the public to do that, all you're going to get is a bunch of account lockouts.
If you have a company or government infrastructure that uses tokens, you don't have that problem, because your administrator verifies your ID and recovers it for you.
I agree this is an issue, but it's solvable.
At the very least, you can offer one-time 2FA bypasses by verifying identify in some other much rigorous and inconvenient way. For example, having the person submit a copy of their drivers license and charging a nominal fee to their credit card. Or, you can allow a one-time SMS-based 2FA once you've verified that the person is in actual possession of their phone and the sim hasn't been jacked.
I understand that from a support standpoint all of that is more expensive. But security has a cost, right?
What I don't accept is that we standardize around a method that is known to be insecure - SMS.
There are a significant number of people who show message previews, something which is on by default, and as such you don't have to unlock the phone to see the code.
I really wish Banks, among others, would let me actually disable SMS 2FA since, as others have noted above, is a false sense of security. Plenty of other options for 2FA like Authy, Google Authenticator, or Yubikey (especially now that it plugs into your phone).
My credit union’s suggestion to me was to set my 2 factor to email only then protect my email with an authenticator app and a yubikey as a backup. Unfortunately for my capital one account the app only seems to support sms.
I still raise an eyebrow with those that send out these 1 time codes, this goes for both to iOS and Android, in that the message component of it before the code is way too short.
There are a significant number of people who show message previews, something which is on by default, and as such you don't have to unlock the phone to see the code. Exactly how is this a security measure given most people get security breached by someone they know. It is these people who are significantly more likely to be in the physical vicinity of the receiving device that we need defending against as opposed some arbitrary turd on the other side of the planet.
All they need to do is lengthen what they're sending a bit so that the actual code does not appear in a message preview.