News for hackers. Stuff that matters.
Re:Google Chrome Keystone is modifying /var symlink on non S... by teamspirit on Tuesday September 24, 2019 @06:37PM (#21065381)
So this caused me to have to reinstall the OS yesterday. Glad to know what the issue was.

And if anyone wants to know, I have to disable SIP because Apple won't let me use an eGPU on my Macbook with TB2.

Re:Google Chrome Keystone is modifying /var symlink on non S... by chmarr on Tuesday September 24, 2019 @07:06PM (#21065630)
Have you tried going into System Preferences, Security, Advanced (I think it's "advanced", it's at the bottom right of the screen.) There you'll find a list of drivers, or something, that you can enable. I can't be more specific than that since my mac here is under IT control, and the feature is disabled.
Re:Google Chrome Keystone is modifying /var symlink on non S... by saagarjha on Tuesday September 24, 2019 @07:30PM (#21065847)
I believe those are the instructions for kernel extensions that are "approved" but distributed by third-parties.
Re:Google Chrome Keystone is modifying /var symlink on non S... by stunt on Thursday September 26, 2019 @07:32AM (#21079941)
Someone here suggested that you could do `csrutil enable --without kext` to load untrusted kernel extension without disabling SIP entirely.
Re:Google Chrome Keystone is modifying /var symlink on non S... by J5892 on Wednesday September 25, 2019 @03:56PM (#21074645)
I was in the same boat. I just happened to come across a years-old forum post mentioning the `/var` symlink right before I reinstalled the OS.
Re:Google Chrome Keystone is modifying /var symlink on non S... by jen20 on Wednesday September 25, 2019 @07:55AM (#21069842)
Historically I've kept SIP disabled to be able to use Dtrace, which was neutered by it. Sure won't be installing any Google software though...
Re:Google Chrome Keystone is modifying /var symlink on non S... by stunt on Thursday September 26, 2019 @07:25AM (#21079922)
As rgovostes already pointed out, you could use `csrutil enable --without dtrace` instead.
Re:Google Chrome Keystone is modifying /var symlink on non S... by mehrdadn on Tuesday September 24, 2019 @06:51PM (#21065492)
Interesting, why can't you do that with SIP? (not a Mac user)
Re:Google Chrome Keystone is modifying /var symlink on non S... by teamspirit on Tuesday September 24, 2019 @06:58PM (#21065560)
From what I understand, Apple removed the ability for TB2. In order to use an eGPU, some system files need to be patched [0].

0. https://github.com/mayankk2308/purge-wrangler

Re:Google Chrome Keystone is modifying /var symlink on non S... by dictum on Tuesday September 24, 2019 @07:04PM (#21065611)
Can't they be patched once, and then re-patched when system updates change make changes to system files?
Re:Google Chrome Keystone is modifying /var symlink on non S... by month13 on Tuesday September 24, 2019 @10:47PM (#21067100)
Could, it's just a hassle.

I'm in a similar boat with a kext that enables unsupported Thunderbolt 3 docks.

Re:Google Chrome Keystone is modifying /var symlink on non S... by dictum on Wednesday September 25, 2019 @10:40AM (#21071208)
Yep. I make some changes that SIP would catch, but I'm mostly comfortable with the boot into Recovery -> run a script -> boot back again. It's not kext stuff, though.

I might have to use PurgeWrangler for an older iMac. Apparently, can keep it mostly enabled, but you need to mind updates and be ready to recover if your modifications are invalidated https://github.com/mayankk2308/purge-wrangler/issues/2#issue...

Re:Google Chrome Keystone is modifying /var symlink on non S... by saagarjha on Tuesday September 24, 2019 @06:54PM (#21065530)
Presumably the driver is not signed with a kext developer certificate, which means SIP must be disabled for macOS to load it.