3 ms·

They probably just don't want to break a bunch of applications that haven't updated yet. It would be nice if they could make it a configurable option for those

They probably just don't want to break a bunch of applications that haven't updated yet. It would be nice if they could make it a configurable option for those of us who don't use / care to use apps that are still not using HTTPS. "Allow Secure Connections Only" checkbox in Settings or something.

sigjuice 10y ago
IMHO, it is not Apple's style to make such things configurable.
wilg 10y ago
Having a configurable option to disable a security setting is a pretty bad idea. Users who don't know anything about security will just disable it forever the first time an app tells them to.
- 0xFFC 10y ago
  I think you missed the idea, It could be temporary thing for a while, after a year or two and with continues beforehand notification, apple could disable non-secure connection apps definitely. kind of like transition period.
  - dogma1138 10y ago
    No there shouldn't be a configurable setting; giving users a choice just creates problems; giving developers a way out just delays implementation. As long as there is a way for an App to make non-SSL connection you'll have to run a non-SSL enabled endpoint; which in effect can put users at risk even if they haven't configured their own devices/apps to use it.
- JoshTriplett 10y ago
  > Having a configurable option to disable a security setting is a pretty bad idea. I think the proposal was to have a configurable option to enable an extra security lockdown, which would remain disabled by default.
  - duskwuff 10y ago
    At which point, it essentially becomes a "break some of my apps in confusing and inexplicable ways" button. Related reading: http://limi.net/checkboxes-that-kill http://limi.net/checkboxes-that-kill
- vel0city 10y ago
  to get this app to work, run: $ sudo setenforce 0 problems solved!
- Karunamon 10y ago
  Not having a configurable option to disable a security setting that's getting in the way of my ability to do what I want on my computer is a worse idea.
ClassyJacket 10y ago
No, the original plan was only to apply the rule to newly updated apps anyway.
mtgx 10y ago
Maybe, but the "indefinite" thing is stupid. Make it 3 years if you must, but do set a deadline. Making it indefinite just means a good portion of the app developers will never even give this a second thought anymore.
- pvg 10y ago
  There's no 'indefinite' and there will be a new deadline - that's right there in the linked thing.
mrpippy 10y ago
This was going to be an App Store certification change, requiring newly-submitted/updated apps that broadly opt-out of ATS to provide a justification. Existing approved apps would continue to run the same.

sigjuice 10y ago

IMHO, it is not Apple's style to make such things configurable.

wilg 10y ago

Having a configurable option to disable a security setting is a pretty bad idea. Users who don't know anything about security will just disable it forever the first time an app tells them to.

0xFFC 10y ago
I think you missed the idea, It could be temporary thing for a while, after a year or two and with continues beforehand notification, apple could disable non-secure connection apps definitely. kind of like transition period.
- dogma1138 10y ago
  No there shouldn't be a configurable setting; giving users a choice just creates problems; giving developers a way out just delays implementation. As long as there is a way for an App to make non-SSL connection you'll have to run a non-SSL enabled endpoint; which in effect can put users at risk even if they haven't configured their own devices/apps to use it.
JoshTriplett 10y ago
> Having a configurable option to disable a security setting is a pretty bad idea. I think the proposal was to have a configurable option to enable an extra security lockdown, which would remain disabled by default.
- duskwuff 10y ago
  At which point, it essentially becomes a "break some of my apps in confusing and inexplicable ways" button. Related reading: http://limi.net/checkboxes-that-kill http://limi.net/checkboxes-that-kill
vel0city 10y ago
to get this app to work, run: $ sudo setenforce 0 problems solved!
Karunamon 10y ago
Not having a configurable option to disable a security setting that's getting in the way of my ability to do what I want on my computer is a worse idea.

ClassyJacket 10y ago

No, the original plan was only to apply the rule to newly updated apps anyway.

mtgx 10y ago

Maybe, but the "indefinite" thing is stupid. Make it 3 years if you must, but do set a deadline. Making it indefinite just means a good portion of the app developers will never even give this a second thought anymore.

pvg 10y ago
There's no 'indefinite' and there will be a new deadline - that's right there in the linked thing.

mrpippy 10y ago

This was going to be an App Store certification change, requiring newly-submitted/updated apps that broadly opt-out of ATS to provide a justification. Existing approved apps would continue to run the same.