Disable gatekeeper notarisation check without disabling SIP

gatekeepernotarizationsip

I am running into this issue where MacOS does security checks on new executables over the network. This introduces a significant delay when first running a new executable. It's very annoying when developing code because the executables are almost always new.

Is there any way to disable this check without disabling SIP?

Best Answer

Aha, I didn't find a way to disable it system-wide for all apps, but you can disable it for specific apps in System Preferences -> Security & Privacy -> Privacy -> Developer Tools

Related Solutions

MacOS – El Capitan, make check, DYLD_LIBRARY_PATH

It seems like DYLD_* only gets stripped out for “protected” binaries (I’m not sure exactly what that means, but apparently anything in /bin and /usr/bin for starters) However, if you copy /usr/bin/env to somewhere else, it gets to keep its DYLD_* stuff:

$ cp /usr/bin/env ~/Desktop; (DYLD_FOO=bar ~/Desktop/env)|grep DY
dyld: warning, unknown environment variable: DYLD_FOO
DYLD_FOO=bar

I think make always runs commands via /bin/sh, so you can’t set “dangerous” variables in the makefile and have them affect the commands, but maybe you could move the test into a shell script, set the environment variables inside the script, and then invoke the script from make. Though obviously, this won’t help you if the tests, in turn, rely on shell scripts (or if the things tested are shell scripts!) because then they’re going to invoke /bin/sh and lose the variables again...

MacOS – Does disabling “System Integrity Protection” in El Cap cause shutdown/restart/logout issues

This was a software issue, after all. Once I upgraded to macOS High Sierra I was once again able to reboot normally, regardless of SIP status.

Best Answer

Related Solutions

MacOS – El Capitan, make check, DYLD_LIBRARY_PATH

MacOS – Does disabling “System Integrity Protection” in El Cap cause shutdown/restart/logout issues

Related Question