News for hackers. Stuff that matters.
Re:iPhone update for Meltdown-Spectre: before/after performa... by StringyBob on Wednesday January 10, 2018 @02:55PM (#16118388)
Wow. After ios 10.2.1 halved performance on my iphone 6 due to the battery issues, I next avoided 11.0 as I accepted responsiveness would be slower on the older iphone6 model.

Now if we want these security fixes that's another -40%... Yikes!

However, it looks like ios 11.2.2 and a new battery is still slightly faster than ios 10.3.3 and an old battery! (geekbench single/multi core score from article of 924/1616 vs my 844/1379)

Re:iPhone update for Meltdown-Spectre: before/after performa... by intopieces on Wednesday January 10, 2018 @03:00PM (#16118438)
I don't understand this logic at all. The fixes are being made for a reason... avoiding the update just means you are getting more performance for a less secure system. Are you betting on a law of averages to break in your favor? Hoping you're not a target of hackers? what am I missing with this strategy?
Re:iPhone update for Meltdown-Spectre: before/after performa... by untog on Wednesday January 10, 2018 @03:04PM (#16118490)
The OP doesn't seem to suggest that they won't update, just that there is a considerable price to be paid in doing so.

> Are you betting on a law of averages to break in your favor? Hoping you're not a target of hackers?

Aside from anything else, I wouldn't be at all surprised if some people do take this gamble. They shouldn't, but if they're informed about it then it's in their own hands.

Re:iPhone update for Meltdown-Spectre: before/after performa... by qeternity on Wednesday January 10, 2018 @03:04PM (#16118491)
All of these issues require local execution. It’s perfectly fine for many single user, performance critical use cases to make this type of security trade off.
Re:iPhone update for Meltdown-Spectre: before/after performa... by mkagenius on Wednesday January 10, 2018 @03:30PM (#16118748)
> local execution

Delivered via JavaScript

Re:iPhone update for Meltdown-Spectre: before/after performa... by euroclydon on Wednesday January 10, 2018 @03:36PM (#16118812)
So don't browse the web from your server. Why are we updating servers?
Re:iPhone update for Meltdown-Spectre: before/after performa... by pdpi on Wednesday January 10, 2018 @03:54PM (#16118998)
It wouldn't be the first time that a buffer overflow somewhere led to arbitrary code execution. What we're patching is a mechanism that allows escalating from unprivileged execution to reading kernel memory, and a mechanism that defeats KASLR
Re:iPhone update for Meltdown-Spectre: before/after performa... by mkagenius on Wednesday January 10, 2018 @03:47PM (#16118919)
Coz you share virtual machines where others run code.
Re:iPhone update for Meltdown-Spectre: before/after performa... by StringyBob on Wednesday January 10, 2018 @03:03PM (#16118485)
Just that I could be looking at a > 75% performance reduction on the same phone compared to when it was new due to the combo of battery degradation, security fixes and ios9 to ios11 general slow down.

I think that if they've disabled some cpu core features that might reduce the maximum power loading anyway and make the double whammy impact of security and battery related slowdown unnecessary.