3 ms·
An important thing to recognize is that every version of macOS (and iOS!) so far has retained some official way to boot a custom/unsigned/"unclean" kernel, spec
by derefr 6y ago
An important thing to recognize is that every version of macOS (and iOS!) so far has retained some official way to boot a custom/unsigned/"unclean" kernel, specifically for kernel (or kernel extension) development.
When SIP (rootless v1) was introduced, macOS came with a way to disable it, for the sake of kernel developers. When APFS was introduced by default, macOS retained two workarounds for kernel developers: both the ability to boot from alternate APFS volumes within the APFS container; and also the ability to install to/boot from HFS+. And when the system volume became truly read-only in Catalina (rootless v2)—that's right, even that restriction could be overridden via csrutil, specifically to facilitate kernel development.
Apple is never going to lock themselves out of booting custom OSes that are almost, but not quite, macOS; because that's how new macOS gets made.
And, of course, as long as you can boot something that's not literally macOS; then that same mechanism can always be abused to boot something that is much less macOS, or in fact not macOS at all (but may still seem to be macOS, from the bootloader's perspective.)
- comex 6y agoNitpick: SIP and rootless are the same thing.
- deleted 6y ago[deleted]
- saagarjha 6y agoFollowup nit: the read only system partition is named as such and pronounced as an acronym.
- michaelmrose 6y agoCouldn't they retain 100% of the capability and lock everyone else out of it via signed software? For others that need to cooperate could they not hand out the capability to dozens of manufacturers without also providing that capability to millions of customers.
- saagarjha 6y agoApple doesn’t really seem to like ceding that control to users that way. It’d be really nice if you could change the root of trust on your device, but with Macs it’s either Apple or nothing, and on iOS it’s just Apple.
- pjmlp 6y agoExcept that the future is user space only extensions, as they re-iterated once more at this year's WWDC, while announcing additional support for newer userspace extensions APIs. So actually, going forward they only need to make it easier for their own kernel teams, not third parties.
- saagarjha 6y agoI would hope that there is always a way to get code execution in kernelspace, though it may require flipping more and more switches.
- pjmlp 6y agoFrom the contents of the talks it is obvious that if that exists, it will be for Apple internal access only. Given how they keep stressing the security and kernel stability during those sessions. They are turning macOS into a proper micro-kernel, by changing the engines while keeping the plane flying.