Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
iOS 10 Beta Features Unencrypted Kernel Making it Easier to Discover Vulnerabilities
- Thread starter MacRumors
- Start date
- Sort by reaction score
Darwin has provided this hand out of instructions for a long time now, and is constantly being updated to reflect. Ahile the unencrypted binary in iOS's flavor may make it easier to find holes, it doesn't make iOS any less or any more secure. The unencrypted binary is nothing near the sensitivity of releasing a source.
I use my ipad in my car and have to jailbreak to have it turn on and off with the power.
Standard Macrumors forum M.O. I can't wait until the next noob poster creates a thread about how closing all apps helps their memory and battery consumption!
Hahah, me too. Probably buried somewhere with the countless "How is battery life" threads after every update, 5 mins after release.
This week in particular I have seen so much nonsense that will probably last a lifetime. Its quite entertaining actually
Right, it's still the same code either way. Sure, in the long run it can help security, but for now it's ripe for reverse engineering and someone to hold onto security flaws for their own purposes. Not that they aren't hard to find in binary form or that there would be plenty left unflagged by analysis tools.
I just find it odd to have made such a decision without any announcement or comment. Obviously the image was encrypted for a reason, they would have to have some explanation to forego that this time around and there's nothing but silence. WWDC would have been a good time to mention this to get more people contributing.
If this was unintentional, then it's probably too late to put the cat back in the bag. Haven't we seen some iOS releases in the past where the build process wasn't what it was supposed to be? That's what this smells like to me.
Oops... Somebody made a big mistake... This is not intentional.
64-bit kernel is left unencrypted, while 32-bit is encrypted!
64-bit kernel is left unencrypted, while 32-bit is encrypted!
But it does. Facebook and other apps use tricks like playing blank audio to stay open longer.Standard Macrumors forum M.O. I can't wait until the next noob poster creates a thread about how closing all apps helps their memory and battery consumption!
Not gonna bite on that bait.
(but I know certain apps do stuff, but generally... They don't)
IDK what you're defining as "generally." Facebook is a pretty popular app, and others abuse the system. Besides abusive apps, any app with Background App Refresh will drain your battery if you have that enabled (default is enabled).Not gonna bite on that bait.(but I know certain apps do stuff, but generally... They don't)
There are even certain ways they can wake up without Background App Refresh, like significant change of location and push notifications, unless the app was force-quit. So it seems like force-quitting is your only defense against that! See: http://stackoverflow.com/questions/...e-background-if-it-was-force-quit-by-the-user "amazingly you even cannot see it from app switcher"
Last edited:
That would be an exception and not the rule by far. And even with something like that, it might make sense for some to close the particular app I question after using it, but it doesn't apply to just blindly closing all apps (which is what was mentioned originally). That said, this isn't what this thread is about, so it's rather moot in that sense.
[doublepost=1466645823][/doublepost]
Background App Refresh doesn't control the ability of an app being able to do something in the background, it's simply another method that can allow an app to do something in the background at times.
. Keep it going.