Wowfunhappy 2 days ago

Because Google majorly screwed up, in a piece of software that runs with administrator privileges! Why the heck was it running with those privileges in the first place?! It's kind of nuts that Google faced basically no blow-back for rendering people's systems unbootable.

The Chrome updater could also have had a bug that completely deletes your home directory, and SIP wouldn't protect you. I guess your computer would still boot in that case, but how much would you care? The actual damage would be worse.

Anyway, this entire incident was notable precisely because it was so unusual—in ~9 years of SIP I'm not aware of any other instances where turning it off caused problems.

Reply View 2 replies
  • saagarjha 2 days ago

    It is trivial to escalate to root and then do precisely that when SIP is disabled.

    Reply View 1 reply
    • Wowfunhappy a day ago

      That's because more recently Apple introduced an entitlement to make that trivial, right? I wish they hadn't done that.

      Reply View 0 replies