3 ms·

what is the rationale for disabling SIP? not only there should be no way to disable this protection, it should be a deliberate design goal to prevent any proce

what is the rationale for disabling SIP? not only there should be no way to disable this protection, it should be a deliberate design goal to prevent any process or application from accessing protected areas.

saagarjha 7y ago
> what is the reationale for disabling SIP? Loading unsigned drivers for eGPUs. > not only there should be no way to disable this protection, it should be a deliberate design goal to prevent any process or application from accessing protected areas. I think you're looking for iOS.
- java-man 7y ago
  iOS: https://www.cvedetails.com/product/15556/Apple-Iphone-Os.html?vendor_id=49 https://www.cvedetails.com/product/15556/Apple-Iphone-Os.htm... loading dev drivers should be done differently, and limited to dev, not production. the fact that one needs to disable security feature in production indicates a bad design. i.e. the user may explicitly allow loading of particular objects (using hashes).
  - saagarjha 7y ago
    I don't understand why you're linking to a CVE list.
httpsterio 7y ago
Some gpus need SIP on off because the drivers won't run else. I generally also have to disable it because I run some apps and modify some underlying behaviours in macOS that I find undesirable. I don't think it should be any worse than running stuff as sudo on Unix, where you can easily break the whole OS if you, as the user, don't know what you're doing. Chrome had a bug and even if it wouldn't have broken the system had SIP been enabled, it's still a serious bug on chrome's side.
protomyth 7y ago
Perhaps if Apple would let us self-sign drivers on our computers, we wouldn't need to disable SIP. Security that does not allow the actual use of the computer gets disabled.
- EricE 7y ago
  Exactly. Apple still hasn't come to terms with balancing security with functionality.
- dreamcompiler 7y ago
  Yes, 100% this. SIP is badly designed because it's a global hammer like root. As such, it prevents power users from doing quite legitimate things with their computers and so we have to turn it off. SIP should work like sudo, not like meta-root.
- GeekyBear 7y ago
  You can whitelist a kext. https://eclecticlight.co/2019/06/01/how-to-bypass-mojave-10-14-5s-new-kext-security/amp/ https://eclecticlight.co/2019/06/01/how-to-bypass-mojave-10-...
  - saagarjha 7y ago
    I'm fairly sure this only applies to KEXTs that are signed but not notarized.
damnyou 7y ago
Sometimes you want to do things that the OS maker does not want you to do, like run dtrace on system binaries. If you had no recourse to bypass the OS maker, the world would be a much worse place.

saagarjha 7y ago

> what is the reationale for disabling SIP? Loading unsigned drivers for eGPUs. > not only there should be no way to disable this protection, it should be a deliberate design goal to prevent any process or application from accessing protected areas. I think you're looking for iOS.

java-man 7y ago
iOS: https://www.cvedetails.com/product/15556/Apple-Iphone-Os.html?vendor_id=49 https://www.cvedetails.com/product/15556/Apple-Iphone-Os.htm... loading dev drivers should be done differently, and limited to dev, not production. the fact that one needs to disable security feature in production indicates a bad design. i.e. the user may explicitly allow loading of particular objects (using hashes).
- saagarjha 7y ago
  I don't understand why you're linking to a CVE list.

httpsterio 7y ago

Some gpus need SIP on off because the drivers won't run else. I generally also have to disable it because I run some apps and modify some underlying behaviours in macOS that I find undesirable. I don't think it should be any worse than running stuff as sudo on Unix, where you can easily break the whole OS if you, as the user, don't know what you're doing. Chrome had a bug and even if it wouldn't have broken the system had SIP been enabled, it's still a serious bug on chrome's side.

protomyth 7y ago

Perhaps if Apple would let us self-sign drivers on our computers, we wouldn't need to disable SIP. Security that does not allow the actual use of the computer gets disabled.

EricE 7y ago
Exactly. Apple still hasn't come to terms with balancing security with functionality.
dreamcompiler 7y ago
Yes, 100% this. SIP is badly designed because it's a global hammer like root. As such, it prevents power users from doing quite legitimate things with their computers and so we have to turn it off. SIP should work like sudo, not like meta-root.
GeekyBear 7y ago
You can whitelist a kext. https://eclecticlight.co/2019/06/01/how-to-bypass-mojave-10-14-5s-new-kext-security/amp/ https://eclecticlight.co/2019/06/01/how-to-bypass-mojave-10-...
- saagarjha 7y ago
  I'm fairly sure this only applies to KEXTs that are signed but not notarized.

damnyou 7y ago

Sometimes you want to do things that the OS maker does not want you to do, like run dtrace on system binaries. If you had no recourse to bypass the OS maker, the world would be a much worse place.