Hi all, I would like to know if kext consent can still be disabled on Apple Silicon Macs. I tried `spctl kext-consent disable` in recovery OS, but after rebooting `spctl kext-consent status` still returns ENABLED. Is this command disabled or something?
Mac Studio
On an M-series Mac you need to reduce system security using the information in the following Apple article:
Change security settings on the startup disk of a Mac with Apple silicon - Apple Support
FYI, you really should not be doing this. Instead you should either be putting pressure on the app developer to update their software so reducing system security is not needed, or you should be finding alternative software that does not require you to compromise system security like this.
As my colleague has mentioned
To add additional info on this Their Party Kernel Extension issue
Kernel extensions with System Integrity Protection
This approach allows Permissive Security flows for developers or users who aren’t part of the Apple Developer Program to test kexts before they’re signed.
I have already disabled SIP completely and have set permissive security. I my case here, the developer, well, is myself. I test kexts either made by myself or from some other devs, a lot of the times they don't have signatures at all. By disabling SIP I already killed kext signature enforcement, I just wanted to disable user consent process so I don't have to allow it to load and reboot every single time I update/add a kext, if that's at all possible on Apple Silicon.
To get the full available options for spctl
In Terminal use man spctl
Kext user consent cannot be disabled on Apple Silicon?
