Talk:System Integrity Protection

List of protected directories correct?
Are we sure the list of protected directories is accurate? According to my testing, /tmp is freely writeable in 10.11.3. Kurt (talk) 20:47, 5 February 2016 (UTC)


 * /tmp isn't a directory, so it definitely doesn't belong in a list of protected directories. It's a symbolic link to /private/tmp; the symbolic link is protected, but /private/tmp is not protected (and you'd break tons of software if you made it protected).  I've fixed the list. Guy Harris (talk) 21:02, 5 February 2016 (UTC)

According to Apple  and   are not protected in El Capitan. --Loopkid (talk) 00:21, 22 February 2016 (UTC)


 * Same story - /etc and /var are symlinks to directories in /private; the symlinks are protected by the target directories aren't. Guy Harris (talk) 00:34, 22 February 2016 (UTC)


 * I have to admit that this was my mistake. I got the list of directories from the Ars review and was able to confirm the file attribute on these. Given that there is now no reliable source for these, should we not remove that sentence altogether?–Totie (talk) 15:07, 22 February 2016 (UTC)

Rename into OS X System Integrity Protection
I think this page should be renamed to OS X System Integrity Protection to make it easier to google. Speculatrix (talk). What do people think?
 * Why do you think that it becomes easier to google? Typing the current name will bring me here, in fact, it is the very first result. Nevertheless, I do not think that it is established Wikipedia policy to name articles after SEO considerations. This is the official name as well as the name currently favoured in secondary sources.–Totie (talk) 15:04, 22 February 2016 (UTC)