News for hackers. Stuff that matters.

A comment on Google Chrome Keystone is modifying /var symlink on non SIP Macs causing k-panic. Parent comment

Re:Google Chrome Keystone is modifying /var symlink on non S... by apostacy on Tuesday September 24, 2019 @11:40PM (#21067384)
I usually do chflags schg instead of chmod 000. I know it might seem like overkill, but Google is very sneaky, and I would not put it past Keystone to just change the permissions for itself.
[ Parent | on HN ]
Re:Google Chrome Keystone is modifying /var symlink on non S... by masklinn on Wednesday September 25, 2019 @02:50AM (#21068362)
> I would not put it past Keystone to just change the permissions for itself.

From experience, they absolutely do it.

[ Parent | on HN ]
Re:Google Chrome Keystone is modifying /var symlink on non S... by apostacy on Wednesday September 25, 2019 @09:02AM (#21070326)
They would call it "repairing permissions". OK, so I didn't break into someone's house, I just "repaired" their door that had locked me out.
[ Parent | on HN ]
Re:Google Chrome Keystone is modifying /var symlink on non S... by Scapeghost on Wednesday September 25, 2019 @06:22PM (#21076241)
> I usually do chflags schg instead of chmod 000.

Thank you. This was the best tip to come out of this whole discussion.

I'll identify every location Google apps write to, and lock them out with this.

[ Parent | on HN ]
Re:Google Chrome Keystone is modifying /var symlink on non S... by dreamcompiler on Wednesday September 25, 2019 @01:31AM (#21067909)
That's very hardcore, but I agree with your logic.
[ Parent | on HN ]