Hacker News new | ask | show | jobs
by Wowfunhappy 2601 days ago
All it takes to disable Gatekeeper is a single Terminal command. All it takes to disable System Integrity Protection is a single Terminal command run from recovery mode. By my count, that is ten minutes of work at most to allow not just unsigned software but unsigned drivers that run at a super low level.

Add in a few more Terminal commands and you can even disable really arcane things like amfi [1]. I don't know why you'd ever want to do that, and it's probably a bad idea, but you can, so by all means please go nuts.

When Apple starts taking away Terminal commands you are free to start screaming, and I'll be there with you. For now, all Apple has ever done on macOS is remove UI options, which keeps inexperienced users from running into them.

---

[1] https://github.com/stek29/nvram-liber-macos

P.S. Microsoft, by contrast, does not let you permanently disable driver signing on 64 bit Windows 8/10. This perpetually drives me nuts, but no one else seems to care for some reason...

1 comments

>Microsoft, by contrast, does not let you permanently disable driver signing on 64 bit Windows

Have you tried the next? (I haven't tried it because I don't have access to a Windows box on which I have admin privs.)

https://windowsreport.com/driver-signature-enforcement-windo...

Test mode and `nointegritychecks` work for some drivers and not others—I've never been able to figure out why. Monitor EDID overrides are a quick example of what doesn't work in test mode. You need go through the whole advanced startup process, which only takes effect until the next reboot.