![]() This moment of silence has been brought to you by Apple media relations. The Register asked Apple whether a fix is planned prior to its next M1 release, said to be designated M1X and expected to power a future MacBook Pro update. "And then it turned out that removing that feature made it much harder for existing OSes to mitigate this vulnerability." "Basically, Apple decided to break the Arm spec by removing a mandatory feature, because they figured they'd never need to use that feature for macOS," he explains in his post. So, to fix this, they'd have to re-design the entire thing to work as a Type 1 hypervisor." ScreenFlow is powerful, easy-to-use screencasting software for the Mac. "The macOS virtualization framework only supports running as a Type 2 hypervisor. "Mitigating the problem requires running your OS at EL1, where the problem register can be disabled, and then having at least some kind of minimal hypervisor at EL2 to deal with those traps (otherwise running an app that uses the register would just crash your machine instead)," explains Martin.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |