Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
Not open for further replies.
Actually it can be patched, there is a flag that can be enabled to run such code in a secure way. So it's not really an issue.
 
  • Like
Reactions: krspkbl
Actually it can be patched, there is a flag that can be enabled to run such code in a secure way. So it's not really an issue.
Has a patch been released? Has anyone measured the impact of the patch on performance? Is this issue fixed in M4 by design not patch?
 
Has a patch been released? Has anyone measured the impact of the patch on performance? Is this issue fixed in M4 by design not patch?
Nobody knows except Apple.

A cpu exploit might need a bios/firmware update to change the microcode instead of just a MacOS patch but Apple will patch it if they haven't already. The M4 might have a hardware fix like the spectre/meltdown exploits on x86 cpus years ago.

Too early to say. We only have M4 in the iPad Pro so far.
 
Less of an issue for end users. I mean you're going to have a process whacking your CPU hard for an hour on your computer to extract a key which probably isn't in RAM anywhere for very long (or at least shouldn't be). There are likely many more lower hanging fruit than that!

This sort of thing is much more of a problem in cloud servers because you can extract keys across logical tenants on a hypervisor potentially. x86-64 scared me a lot more than this.
 
  • Like
Reactions: You’re not me
Status
Not open for further replies.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.