←back to thread

2603 points mattsolle | 1 comments | | HN request time: 0.246s | source
Show context
submeta ◴[] No.25075156[source]
Unbelievable. When I read the tweet (tried to post here as well), I suddenly realized why my Mac was unresponsive an hour ago.

Here is another tweet that describes the problem in more detail:

https://mobile.twitter.com/llanga/status/1326989724704268289

> I am currently unable to work because macOS sends hashes of every opened executable to some server of theirs and when `trustd` and `syspolicyd` are unable to do so, the entire operating system grinds to a halt.

EDIT:

As others pointed out, I put this to my `/etc/hosts` file and refreshed it like so:

    sudo emacs /etc/hosts # add `0.0.0.0 ocsp.apple.com` 
    sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder # refresh hosts
replies(26): >>25075338 #>>25075481 #>>25075547 #>>25075666 #>>25075887 #>>25076053 #>>25076387 #>>25076568 #>>25076811 #>>25077902 #>>25077923 #>>25077940 #>>25079234 #>>25079856 #>>25079879 #>>25080093 #>>25080357 #>>25080370 #>>25080849 #>>25081772 #>>25081989 #>>25083938 #>>25087820 #>>25090415 #>>25090991 #>>25095226 #
read_if_gay_ ◴[] No.25075547[source]
I started panicking mildly thinking my drive was failing or something.

And just before this, I finally managed to fix Spotlight pegging one core at 100% constantly. Next thing, I reboot into a laggy system. macOS is my favorite OS, but the shit I put up with... it's basically an abusive relationship at this point.

replies(10): >>25075694 #>>25075845 #>>25075881 #>>25075908 #>>25076012 #>>25076608 #>>25079197 #>>25079319 #>>25080929 #>>25085281 #
nomel ◴[] No.25076608[source]
I never have problems with the new MacOS or iOS. The trick is to just wait for the X.1 update.
replies(1): >>25076816 #
pavon ◴[] No.25076816[source]
This is happening to Macs running Catalina and Mojave, not just those that upgraded to BigSur.
replies(1): >>25078553 #
1. JKCalhoun ◴[] No.25078553[source]
High Sierra it is then. ;-)