hello_asdf

Joined 14 years ago

Karma

199

Submissions

104

Member since

Apr 2

View on Hacker News

Recent submissions

Comment · 6 years ago

Interesting, you’re still paying about $5k an hour from what I can see though. If you want to fly private and can afford it, it’s possibly a good deal.

Comment · 6 years ago

Thank you, I didn't know that.

Comment · 6 years ago

There's a few solutions:

LittleSnitch 4 can continue to work (with the kext) on Big Sur following this: [1]

LittleSnitch 5 can block all protected MacOS processes by following this: [2]

Murus can use PF and block IPs for Apple services: [3]. This isn't per process, and is really just a UI for the built-in PF process.

If you'd like to block the notarization check, you can block trustd (/usr/libexec/trustd) access to ocsp.apple.com (on both system and user process ownership in LittleSnitch).

Hope this helps. It's really not as bad as you think, there's a few solutions depending how thoroughly you want to block things.

[1] - https://www.obdev.at/support/littlesnitch/245913651253917

[2] - https://tinyapps.org/blog/202010210700_whose_computer_is_it....

[3] - https://www.murusfirewall.com

Comment · 6 years ago

I believe you can still block the specific destination IPs with pf using murus if you want, but yes it's quite bothersome.

You can find the full list of apps that bypass it here: /System/Library/Frameworks/NetworkExtension.framework/Versions/A/Resources/Info.plist under ContentFilterExclusionList.

Comment · 6 years ago

Yep, I was just noting it for anyone else that tried it and was curious.

Comment · 6 years ago

Yep, it is, I was just noting it in case someone was wondering why it was being wonky after trying it out.

I already did just to test it out, the results include a 'next' link that you can use :)

Comment · 6 years ago