Little Snitch is not necessary. You can block it via the /etc/hosts hack or in some environments you can block this at the router level or with a device like a Pi-Hole.So is Little Snitch not necessary?
The big problem in blocking access to ocsp.apple.com is that you don't know how every single application will react.
I used the /etc/hosts method and was able to fire up macOS Mail during this snafu. However, I left the entry in /etc/hosts and then parts of App Store wouldn't connect.
So I reluctantly removed the /etc/hosts entry yesterday. By then Apple had fixed the underlying OCSP issue.
I consider this a massive F-A-I-L for Apple. I wasn't attempting to download Big Sur, I just wanted to read e-mail on my Mac. When it first failed, I fired up my Windows PC which had no problem connecting to various e-mail accounts. In fact, I read about the /etc/hosts workaround while surfing this site on my Windows PC.
Ultimately, there's really no recourse. Apple's enforcement of OCSP validation has revealed a single point of failure as we saw on Thursday. That's bad design.
Even worse, it invites hackers to DDoS attack ocsp.apple.com because now they know interrupting data packets to that domain will cripple millions of Apple devices. In just a few days, every script kiddie on the planet knows they can inconvenience millions of Mac users by taking out ocsp.apple.com because Apple showed them it was possible.
My guess is that Apple will do nothing. They will make no apology for Thursday clusterf*** and they will keep things status quo.
Steve would have been completely pissed at Thursday's snafu and would have personally apologized (he did this) but Steve has been dead 9+ years. The current Apple management team doesn't have any interest in apologizing for these sort of missteps.
Last edited: