But it also protects Apple from legal and legitimate hacking, illegal hacking, and, last but not least, the user himself or herself.ĭoes this mean that disabling SIP is wrong or risky? Not really. What does SIP protect Apple from? Malware, certainly. (See: About System Integrity Protection on your Mac - Apple Support). It is security protection for Apple, not for the user. People hear something like "System Integrity Protection" and think it is some kind of security architecture to protect them. The key part to remember here is the audience. Here is slightly more information: _Integrity_Protection_Guide/Introduction… This is probably what breaks TotalFinder. The other, more important component of SIP is protecting processes. (But usually there is always another way.) And to tell the truth, it is only a few particularly nasty open-source libraries and Perl modules that are the biggest offenders here. But if the developer is actually trying to modify some existing Apple resource, executable, or config file, then modifying a protected directory might be the only way. Some software will run just fine /usr/local, in that case, there is no point in trying to modify /usr. But you can't really make that determination without analyzing each specific app in question. It is true that a developer that relies on modification of system paths is likely just incompetent or lazy. If you plan to re-install TotalFinder in the future, you can keep this preferences file.There is more to SIP than just protecting directories.
0 Comments
Leave a Reply. |