News for hackers. Stuff that matters.
Re:Apple Delays iOS SSL Requirement Indefinitely by dep_b on Thursday December 22, 2016 @08:26AM (#13237091)
It was always a nice way to force my customers to implement HTTPS, the threat of Apple rejecting or removing the app. It's pretty easy to implement and inexpensive so why people still don't do it is a complete mystery to me.
Re:Apple Delays iOS SSL Requirement Indefinitely by SunboX on Thursday December 22, 2016 @10:49AM (#13238020)
Think of IoT Devices. For example, Sony's NEX Cameras have a build in HotSpot. You connect your phone to it and you have remote control to your camera. This has no HTTPS by now. Apple would break all those remote control apps. And it can't be fixed by releasing a new app version, because you also have to update the cameras.
Re:Apple Delays iOS SSL Requirement Indefinitely by mrpippy on Thursday December 22, 2016 @12:56PM (#13238990)
There are allowances made for local networking.

From the Info.plist key reference (https://developer.apple.com/library/content/documentation/Ge...):

App Transport Security (ATS) applies only to connections made to public host names. The system does not provide ATS protection to connections made to:

* Internet protocol (IP) addresses

* Unqualified host names

* Local hosts employing the .local top-level domain (TLD)

To connect to an unqualified host name or to a .local domain, you must set the value of the NSAllowsLocalNetworking key to YES.

Re:Apple Delays iOS SSL Requirement Indefinitely by seanalltogether on Thursday December 22, 2016 @01:39PM (#13239315)
That's assuming you're using bonjour (zero config). I have 2 clients with thousands of in home devices which are using NetBios to resolve a local ip address and directly connecting over http. I imagine there are many other hardware vendors still using this method out there.
Re:Apple Delays iOS SSL Requirement Indefinitely by mrpippy on Thursday December 22, 2016 @03:50PM (#13240275)
Sounds like the HTTP connection is being made to an IP address, in which case you should be fine.
Re:Apple Delays iOS SSL Requirement Indefinitely by creeble on Thursday December 22, 2016 @12:26PM (#13238749)
It can't even be fixed then because TLS certs aren't possible for LAN connections (or at least not validate-able, which means the same thing).
Re:Apple Delays iOS SSL Requirement Indefinitely by n0d3d3v on Sunday December 25, 2016 @07:34AM (#13253913)
TLS certs are about to be possible for LAN connections with Beame.io's open source SDK, though
Re:Apple Delays iOS SSL Requirement Indefinitely by dep_b on Thursday December 22, 2016 @11:10AM (#13238172)
A good start would be a warning about insecure connections being made by the app.
Re:Apple Delays iOS SSL Requirement Indefinitely by droopybuns on Thursday December 22, 2016 @12:12PM (#13238647)
They had a method for whitelisting vanilla http domains in the app plists. It wasnt going to eliminate http. It was going to push general app transport to TLS by default.

Apple seems to have wildly varying execution. Some things they do are great. Other times their behavior is shockingly erratic.

Re:Apple Delays iOS SSL Requirement Indefinitely by brians on Friday December 23, 2016 @11:12PM (#13248545)
Principally? Reliance on cloud service origins without TLS support. Amazon still has some from acquisitions, for example.
Re:Apple Delays iOS SSL Requirement Indefinitely by 0x0 on Thursday December 22, 2016 @08:49AM (#13237209)
I think you also have to register with some US government body to obtain crypto export licenses yearly. Even if the app just uses the iOS https connection classes!
Re:Apple Delays iOS SSL Requirement Indefinitely by stepanhruda on Thursday December 22, 2016 @08:56AM (#13237239)
No you don't.
Re:Apple Delays iOS SSL Requirement Indefinitely by 0x0 on Thursday December 22, 2016 @11:35AM (#13238335)
It used to be like that, but it seems like this was changed in the last month?! http://stackoverflow.com/a/40919650

For all the downvoters on my parent post: This blog from last year said something else: https://pupeno.com/2015/12/15/legally-submit-app-apples-app-...

Edit: Downvote me all you want, but the OP asked why people just didn't implement HTTPS and I have first hand knowledge of several apps that chose to not implement HTTPS because the legal work required around crypto export licenses was too much to be worth it.

Re:Apple Delays iOS SSL Requirement Indefinitely by stepanhruda on Friday December 23, 2016 @02:33AM (#13243448)
It was always exempt because you weren't shipping your own crypto implementation. Apple has to comply when shipping iOS. Those apps were not shipping HTTPS for a non-reason. This recent change only made the wording clearer in iTunes Connect.
Re:Apple Delays iOS SSL Requirement Indefinitely by 0x0 on Friday December 23, 2016 @06:01AM (#13244160)
The uncertainty around phrasing like "uses encryption" certainly would require spending expensive lawyer hours to ensure the app would be in the clear. Certainly not a "non-reason".
Re:Apple Delays iOS SSL Requirement Indefinitely by jtdowney on Tuesday December 27, 2016 @04:52AM (#13262270)
I've spent time with lawyers on specifically this topic. It is about who is distributing the crypto code. There is also an exemption for open source crypto code. On iOS you definitely do not need to register your app if it is just using the built in HTTPS functionality. Hire your own lawyers if you're really worried about it though.