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.
Apple Releases iOS 11.2.2 With Security Fixes to Address Spectre Vulnerability
- Thread starter MacRumors
- Start date
- Sort by reaction score
Certain ARM architectures (used by Apple) are also vulnerable to out of order execution vulnerabilities in as detailed in Meltdown paper.
What makes you think these were INTEL-only exploits?
Every explanation of the impact of these vulnerabilities explains that ARM and AMD chips are also vulnerable.
Admittedly, the full detail of the flaws is yet to be revealed, but the information available so far suggests all systems need some kind of update or fix to the issue that seems to affect the way (all) operating systems interact with the hardware.
I won't. The last time there was a "huge update" that was "highly recommended", was back during the iOS 7 days. I deliberately kept my devices on iOS 6 because of all the issues and slow-downs with iOS 7, but when a security update was released, I updated my devices and they were never the same again. I've seen what iOS 11 did to my 12.9 iPad Pro... I'll take my chances with my other devices on 10.3.2 and keep them at 10.3.2.
There might be. But if it is like that iOS 7 update, any update for 10.x will only be for those devices not capable of upgrading to 11. If a device was capable of running iOS 7, then in order to get the fix, one needed to update their device to 7 (even if they were running 6)
Just installed it. Looks like they finally resolved the top of the screen turning green like you are in a call when clearing notifications. Thank you!
I ran Geekbench 4 three times directly before and three times directly after the update. Results (averaged) are as follows:
Before:
Single: 4045
Multi: 9777
After:
Single: 4087
Multi: 9807
Seems like they're all basically the same, within a reasonable margin of error.
Before:
Single: 4045
Multi: 9777
After:
Single: 4087
Multi: 9807
Seems like they're all basically the same, within a reasonable margin of error.
Wait.. what? What does battery level have to do with it? Throttling is based on battery wear, not on current charge.
Good luck with that. This is not about others testing the things for you first, this update is a MUST for EVERYBODY and in case it messes with our devices there's nothing we can do about it, welcome to 2018!
Someone doesn’t know about how many of these critical updates are pulled because something was flawed and then rereleased with a new version number.
[doublepost=1515441430][/doublepost]
All something screws up when fixes for “hot bugs” are released.
[doublepost=1515441462][/doublepost]
Please reread the posts above...
Maybe it's more "don't update on the go", since your charging access may be hindered or you will stay out of service for quite some time? Maybe you have this "50% battery" now, but maybe you're skiing and cold temp will get to it and it won't update successfully?
They limited it via recognizing 3G/WiFi but maybe agenda behind it is much more complex.
yeah i get you, anyways apparently these "fixes" are gonna throttle all devices in one way or other so mehhh...damage is done already.
The only REAL fix is gonna come with new hardware and new architecture ant that's gonna take some time (1 year or 2)...
Already did in the other thread and at 65%.
https://forums.macrumors.com/thread...-diagnostic-test.2098675/page-5#post-25662170
Oops......
But the 5 was sold by Apple until Sept 13 and it’s exact brother ( except case) 5C until September 15 - two year support only for that.
You can see lots of examples where Apple continue to sell older hardware ( and independent retailers even longer), yet Apple drops support quickly.
Microsoft gets a bit of a bashing on these forums, but they released a security patch for XP ( released in 2001!) in June last year.
So the most plausible explanation for why the betas have been 11.2.5, not 11.2.2: because Apple knew they would have to insert at least one bugfix release in between for security reasons.
Apple has rarely pushed security updates for previous iOS releases.
They were under embargo; they've known since June, I believe.
That was Meltdown; this is Spectre.
(And Meltdown, too, wasn't Intel-specific. Some ARM CPUs are affected.)
Apple has rarely pushed security updates for previous iOS releases.
They were under embargo; they've known since June, I believe.
That was Meltdown; this is Spectre.
(And Meltdown, too, wasn't Intel-specific. Some ARM CPUs are affected.)
Considering it's a workaround for Safari I don't see how Geekbench results would be affected anyway...
Yup. It happens that I ran mine at 65% for the naysayers here, just to prove a point.
It’s not about the throttle. It’s about how sometimes rushed deployments have led to disasters. Point to case when Apple pulled an Apple Watch update (can’t recall exact WatchOS) because it was bricking Apple Watches. The fix? Swap it for a new one at an Apple Store.
I don’t have access to an Apple Store, so I can’t accidentally brick my iPhone. Hence I let others update and then read reactions.
yes i got you, in MY case IS about the throttle. Even if the update turn fine apprently things are gonna get a little slow from now onwards and that's pretty pretty sad. All the world devices are faulty now, and all are geting old soon.
Last edited:
Ran the benchmarks for Safari (JetStream, ARES-6 and Speedometer). Also ran older ones like Sunspider, Kraken and Octane. All were so close that there’s basically no difference. If I ran each 10 times in a row I might get enough data to average them out and see a difference. For now there were all within 1-2% (faster or slower). Geekbench 4 was also the same.
Only odd thing is JetStream wouldn’t return a score. It showed “NaN” for a result for some tests and for the overall score. I haven’t figured out what that means yet. Anyone else try JetStream yet AFTER the update? Before it worked fine.
Only odd thing is JetStream wouldn’t return a score. It showed “NaN” for a result for some tests and for the overall score. I haven’t figured out what that means yet. Anyone else try JetStream yet AFTER the update? Before it worked fine.
Oops. I neglected to look at the release notes and assumed this was a patch for the OS level vulnerabilities, not just protecting from browser based attacks.
averaging a 400+ point improvement consistently on my 8 plus after the update, which I'm still surprised about.
Nice, good to know....my main worry is my old i7 3770k running windows 7 though....