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

Re:Google Chrome Keystone is modifying /var symlink on non S... by jacobsenscott on Tuesday September 24, 2019 @09:18PM (#21066616)

I certainly understand the desire to rage kill google software update because they messed up, but people shouldn't actually do this because they'll be vulnerable to all future malware that targets chrome. And this varsectomany bug will never happen again.

[ Parent | on HN ]

Re:Google Chrome Keystone is modifying /var symlink on non S... by dreamcompiler on Wednesday September 25, 2019 @12:35AM (#21067641)

This is not rage-killing. I've been doing this for several years because Keystone is a ridiculous resource hog and I fundamentally disagree with the notion that any software should be allowed to run (much less change the configuration of) my machine without my explicit permission. I'm willing to stay on top of the malware situation and update Chrome manually. I wish I didn't have to, but Google leaves me no other option.

[ Parent | on HN ]

Re:Google Chrome Keystone is modifying /var symlink on non S... by prepend on Wednesday September 25, 2019 @02:32AM (#21068268)

I think the probability of Google freaking out and pushing ads to my system is higher than the probability of me a chrome zero day that I give a shit.

They are both very low, but I’d rather programs not change my stuff against my will, even if they are trying to protect me.

[ Parent | on HN ]

Re:Google Chrome Keystone is modifying /var symlink on non S... by robin_reala on Wednesday September 25, 2019 @02:02AM (#21068096)

Only if you continue using Chrome.

[ Parent | on HN ]

Re:Google Chrome Keystone is modifying /var symlink on non S... by Gibbon1 on Wednesday September 25, 2019 @04:36PM (#21075104)

Apple needs to provide the user with the ability to ban software from google and other malign companies.

Problem partly solved.

[ Parent | on HN ]