4 ms·
I would start with LittleSnitch [1] Don't block things by default. Let it learn traffic and show you what is talking to what. Then sort out what things you w
by LinuxBender 6y ago
I would start with LittleSnitch [1] Don't block things by default. Let it learn traffic and show you what is talking to what. Then sort out what things you want to block. I suggest this method because some of the flows won't be obvious if you start selectively blocking things from the start. Make notes of the IP's, CIDR blocks and domains that are problematic and block them on the edge of your network on a monthly basis using data derived from LittleSnitch.
You can also find some blogs and forums that discuss what applications are not critical and that you can "launchctl unload -wF" safely to minimize chatter and improve battery life. Ensure the sites specifically call out the version of MacOS you are on, as these things change with each release.
[1] - https://www.obdev.at/products/littlesnitch/index.html https://www.obdev.at/products/littlesnitch/index.html
- atmosx 6y agoThere was a thread the other day... about this. I believe mapping ocsp.apple.com to 127.0.0.1 on your hosts file will do the trick.
- LinuxBender 6y agoOh if the question was just blocking the OCSP, then yes, /etc/hosts or null route will do that. That isn't the only data leakage (tracking) that comes out of a mac however. sudo route add -net 17.253.17.0 255.255.255.0 -blackhole also works for the OCSP. You will still get some delay in opening applications. I would like to see apple do OCSP stapling and caching in the OS like reverse proxies already do, but that would defeat the tracking I guess.
- jlgaddis 6y agoAnyone wanting to do the above should first check what ocsp.apple.com resolves to for them -- looks like the responses vary by geographical location.