News for hackers. Stuff that matters.
Re:Windows OS, Services and Apps: Network Connection Target ... by jve on Friday May 27, 2022 @07:22AM (#31528264)
You don't want to block all of that. CLR checking (else your apps may become slow to start) and windows updates (else you may become vulnerable) should be enabled.

Someone else has some suggestions?

Re:Windows OS, Services and Apps: Network Connection Target ... by pixl97 on Friday May 27, 2022 @09:44AM (#31529554)
Having CRL/OCSP getting blocked on corporate networks is one of those things I have to commonly troubleshoot. You can get some weird timeouts and failures in applications that can be fun.

For example an internal app starts up fine and works, but then can't connect to github. Instead of showing cert errors, I've had ones show errors that make it appear that you may have a DNS problem or that the connection to github itself was broken.

Re:Windows OS, Services and Apps: Network Connection Target ... by prmoustache on Friday May 27, 2022 @08:18AM (#31528668)
If I was still using windows I would totally block everything and run a wsus server in a VM that has a vlan and firewall config.

The issue is you can only control your firewall at home. Whenever you are out you are pretty sure that MS and Apple bypass any rule you'd put on the local firewall.

I prefer running sane operating systems.

Re:Windows OS, Services and Apps: Network Connection Target ... by jve on Friday May 27, 2022 @12:37PM (#31531562)
Pretty sure your sane OS makes calls to CRL/OCSP lists to validate cert revocation. Many of the calls in that list do just that.