199 karma · joined April 2, 2012
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....
You can find the full list of apps that bypass it here: /System/Library/Frameworks/NetworkExtension.framework/Versions/A/Resources/Info.plist under ContentFilterExclusionList.
I already did just to test it out, the results include a 'next' link that you can use :)
[1] https://developer.spotify.com/documentation/web-api/referenc...
It also helps to weed out people who can’t actually program, this comes up annoyingly often.
I agree that having intentional errors in a starter repository is bad though.
Couple things that I'd like to have:
1. Filter by full pricing
2. Filter by canvas / wood / etc.
3. Filter by oil / acrylic / etc.
This is all speculation though.
https://www.amazon.com/Making-Prince-Persia-Jordan-Mechner-e...
I bought it immediately upon finishing the PDF, and my Kindle's battery is dead..
> his merry band of plaintiffs
> but sour grapes alone do not a lawsuit make
Here's a great playlist I found of it though: https://www.youtube.com/playlist?list=PLhixgUqwRTjzzBeFSHXrw...