Apple has introduced a new security feature in Mac OS X El Capitan (10.11) called System Integrity Protection (sometimes referred to as rootless).
DevOps'ish is on hiatus and is not taking new subscribers at this time. Stay tuned to Chris Short's web site for details on future projects and when DevOps'ish will relaunch.Thank you to all subscribers for your years of support.
What is System Integrity Protection? According to Apple’s documentation:
A new security policy that applies to every running process, including privileged code and code that runs out of the sandbox. The policy extends additional protections to components on disk and at run-time, only allowing system binaries to be modified by the system installer and software updates. Code injection and runtime attachments to system binaries are no longer permitted.
What does it really do? It prevents users, processes, etc. from modifying certain resources on the system (even if you’re running as root).
This is a great security enhancement for the vast majority of Mac users. But, some people need to modify the resources protected by System Integrity Protection.
For example, I compile and use a few GNU utilities (sed for example) so that I don’t have to worry about BSD vs. GNU syntax changes when bouncing between my laptop and servers I’m administering.
Even though the security configuration is stored in NVRAM it is easy enough to disable System Integrity Protection (NOTE: The vast majority of users will never need to do this).
- Reboot Your Mac
- Enter Recovery Mode (hold CMD+R during reboot)
- Go to Utilities -> Terminal
- Reboot Normally
System Integrity Protection will now be disabled; you’re back to having complete control of your operating system again. You can verify the System Integrity Protection configuration by entering
csrutil status in a terminal.
If you want to get down into the nuts and bolts of System Integrity Protection (aka SIP, rootless) I recommend reading Rootfool – a small tool to dynamically disable and enable SIP in El Capitan