Does anyone know what is going on with the 10.11.1 beta? I CANNOT disable SIP! If I go into recovery and run the csrutil disable command, SIP disables. I can run csrutil status and it tells me that SIP is disabled. However, when I reboot it enables automatically!!
Any ideas?
I can't reproduce that on MBPr running 10.11.1.
Note that after disabling SIP in Recovery Mode and then booting normally, csrutil status will report:
System Integrity Protection status: enabled (Custom Configuration).
Configuration:
Apple Internal: disabled
Kext Signing: disabled
Filesystem Protections: disabled
Debugging Restrictions: disabled
DTrace Restrictions: disabled
NVRAM Protections: disabled
This is an unsupported configuration, likely to break in the future and leave your machine in an unknown state.
So it says "enabled (Custom Configuration)" but all it's component parts are disabled and so it is effectivly (and in practice) disabled.
-Max
If this is not the case for you (I have no explaination of why that might be), then you could try enabling SIP from Recovery Mode while selectively disabling components of it, to see if setting it like that persists over multiple boots, by running one of the following commands while booted into Recovery mode:
You can disable two or more components by structuring the command as follows:
csrutil enable --without kext --without debug
Yes, I am getting the same info however the programs that need it to be turned off, are still reporting that it's on!! I'm sure that eventually all apps will comply, but right now some of them must have system access to operate - such as Winclone, and there are several others. SO, this is not working!
Again, this hasn't been the case for me - I've been able to install and run various software that SIP currently prevents. You mention that the software in question actually reports the SIP is on - this implies that it explicitly checks for SIP, rather than failing to be able to write a file to a SIP protected folder and then throwing an error about failing to install. Is that what you meant?
Yes, the software checks to see if SIP is on and reports that it can't operate with SIP. Then the software shuts down. I am getting the error "Operation not permitted while System Integrity Protection is engaged. Perhaps it really isn't on but the software is programmed to think it is on in this version. This is the first time I've used these programs since I installed 10.11.1.
It must itself run csrutil status and then fails to realise that, although it says enabled, that it is, for all intents and purposes, disabled. I suggest you track down a slightly earlier version of the software in question (released no later than June/July, say) and run that instead.
