At its annual World Wide Developer’s Conference (WWDC), Apple’s security experts announced plans to mandate secure network communication via HTTPS for virtually all App Store apps, starting 1 January 2017.
A quick refresher: HTTPS is the secure, encrypted, version of the Hypertext Transfer Protocol – the language that your web browser or app uses when it’s talking to a website.
Using HTTPS instead of HTTP means that any data you send or receive, such as pages, cookies, images, comments, personal data or passwords, is encrypted and therefore unintelligible to anyone trying to eavesdrop on what you’re doing.
On web browsers, the well-known padlock icon says you’re on HTTPS, but on many mobile apps you just can’t tell. Apple’s out to change that. According to Ivan Krstić, Apple’s Head of Security Engineering and Architecture:
By the end of 2016, when your apps communicate with your own server back ends, they must do so using a secure TLS channel using TLS 1.2, unless the data being communicated is bulk data such as media streaming and data that’s already encrypted.
In 2015, Apple introduced App Transport Security (ATS) for iOS 9.0 and OS X 10.11, which enforced HTTPS connections when enabled. With ATS turned on, attempts to establish network connections with insecure HTTP simply fail. But Apple gave developers the option of switching ATS off, and many did so. (Notoriously, Google offered iOS developers “last resort” code designed to evade ATS, thereby enabling non-HTTPS-compliant ad systems to keep serving ads to iOS 9 apps.)
Now, says Apple, ATS will have to be turned on in nearly all cases.
Noting that a gradual industry-wide migration is well underway, TechCrunch observes:
App developers who have been wondering when the hammer would drop on HTTP can rest a little easier now that they have a clear deadline…
Possibly, but not all of them sound quite so relaxed yet.
Apple’s Developer Forums are attracting worried messages from coders who see trouble with apps linked to low-cost (non-HTTPS) sites they host themselves, or sites linked to devices or embedded hardware that can’t be made HTTPS compliant, or large public databases hosted by folks who are unlikely to upgrade to HTTPS by January.
It’ll be interesting to see how many exceptions Apple will be coaxed into offering. But, a year from now, it seems highly likely that most modern mainstream iOS apps will be HTTPS-only. And that can only be good.