4 ms·
SIP is a relatively new feature. This would have been devastating only a few years ago. What Google did was effectively: sudo rm -Rf /var Would you trust
by TimTheTinker 7y ago
SIP is a relatively new feature. This would have been devastating only a few years ago. What Google did was effectively:
sudo rm -Rf /var
Would you trust a program that even attempted such a command on your machine? "But they had SIP disabled" is no defense for software that tries to take destructive action.
SIP is intended to protect against malicious software and against users accidentally hosing their system; there are legitimate reasons for disabling it. This was not anyone's fault but Google's.
- sp332 7y agoI don't think this was intentional or malicious on Google's part. It's only not a defense for the QA team.
- zepto 7y agoWhether it was malicious or not it was unnecessary and irresponsible. It’s not just a QA issue - it’s a design flaw.
- sp332 7y agoI expect it was a typo, like that time Steam deleted people's data on Linux https://www.theregister.co.uk/2015/01/17/scary_code_of_the_week_steam_cleans_linux_pcs/ https://www.theregister.co.uk/2015/01/17/scary_code_of_the_w... , or [edit: ok this one probably isn't relevant] when Adobe CC removed random folders on Macs. https://help.backblaze.com/hc/en-us/articles/217665378--bzvol-is-missing https://help.backblaze.com/hc/en-us/articles/217665378--bzvo...
- deleted 7y ago[deleted]
- magicalist 7y agoIt's a symlink and / has to be writable by the logged in user, so it's actually just effectively rm /var
- KingMachiavelli 7y agoSince when is / writable by any logged in user? Is a MacOS thing?
- acdha 7y agoIt requires the user to have disabled SIP and then used root access to modify it. On a standard install, it's owned by root:wheel with mode 755.
- TimTheTinker 7y agoThanks for the correction!