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 sterlind on Wednesday September 25, 2019 @12:30AM (#21067609)

In a limited way, Windows is better about this sort of thing. System integrity checks (checksums of critical files) can't be disabled, only defeated. All drivers must be signed or you have to enable test signing mode, which requires a reboot and puts annoying text permanently in the corner of the screen.

...but you can still delete whatever you want out of System32 (though it may grow back), and you can add your own things, and dll hijacking is an issue etc. Just when it comes to kernel code are the protections better.

[ Parent | on HN ]

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

I vaguely remember Microsoft pissing off a lot of device makers and users with Vista because it started requiring signed drivers.

I might be remembering it wrong, but I thought it was definitely a good thing and definitely a step forward.

I wish that would happen more often. With so many things moving to the web there's not that many excuses left to sacrifice security and stability for backwards compatibility.

[ Parent | on HN ]