Some more context to this: while a customKC (which is basically "something resembling Mach-O kernel file to transfer control to instead of the original kernel") payload is indeed unsigned, it's hash is still signed by machine-specific key, so chain of trust is preserved.https://twitter.com/never_released/status/1339753170629746690 …
Do you have any good ideas for data recovery? E.g. on my Android phone, I know that once I unlock the bootloader I can always flash/boot some recovery/OS that will let me unlock my encrypted volume and pull data or the raw filesystem.
-
-
Obviously that goes against your normal security model, but for those of us who'd like to *opt in* to the ability to do that, is there a way? Like, is there any path from DFU mode to custom kernel that doesn't involve wiping/partitioning the whole SSD?
-
nope, there's no way to do that from DFU. But given that all security settings on M1 Macs are on a per-OS basis, the easier way to deal with that would just be to leave your main macOS/recoveryOS alone, and then set up N macOSes off to the side which you transition to a custom KC
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.