With the release of the latest OS 'macOS Big Sur' for Mac, it will slow down to OS other than Big Sur
When macOS Big Sur became available, problems such as 'it takes a few minutes to start the application' and 'the response of the entire OS becomes worse' were reported to macOS. This problem is also seen in other versions of the OS, including Catalina and Mojave, regardless of whether or not they are using Big Sur. Other services developed by Apple, such as Apple Pay and Apple TV, have also been reported to slow down.
macOS Big Sur launch appears to cause temporary slowdown in even non-Big Sur Macs | Ars Technica
Mac users couldn't launch apps this afternoon after Apple verification server issue --The Verge
Several Mac users speculate that the issue is due to a process called 'trusted' that checks on Apple's servers to see if Apple's macOS app is notarized. With trustd, macOS tries to connect to a host named 'oscp.apple.com', but this authentication fails repeatedly. It is believed that this causes the system to slow down when trying to launch the app.
Hey Apple users:— Jeff Johnson (@lapcatsoftware) November 12, 2020
If you're now experiencing hangs launching apps on the Mac, I figured out the problem using Little Snitch.
It's trusted connecting to https://t.co/FzIGwbGRan
Denying that connection fixes it, because OCSP is a soft failure.
(Disconnect internet also fixes.) Pic.twitter.com/w9YciFltrb
Python developer Łukasz Langa also said, 'Every time I open an executable file, the Mac sends a hash to Apple's server, and if' trustd 'or' syspolicyd 'doesn't work, the entire OS will stop working, so the work will be done. I can't do it anymore. '
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.— Łukasz Langa ⚡️ (@llanga) November 12, 2020
I'm typing this from my phone since the Mac is effectively frozen. Pic.twitter.com/dWrjyuiXpQ
This issue was also talked about on the bulletin board 'Hacker News' where developers and entrepreneurs gather, and some thought that it was a driver failure. Also, some people have pointed out that the specification of 'sending a request to the server every time the application is started' on the Mac is a problem.
Unbelievable. When I read the tweet (tried to post here as well), I suddenly rea ... | Hacker News
OCSP, which macOS tried to connect to, stands for ' Online Certificate Status Protocol ' (a protocol that verifies the status of certificates online). If the user tries to use the app even though the Apple device cannot connect to the network, the notarized authentication status will be 'Soft Fail'. Apple devices in this state should recognize that 'the user is not online, but allows the application to start'. However, this time the Apple device was able to perform a DNS lookup on oscp.apple.com, so the device side decided that 'being able to perform a DNS lookup should be able to connect to the OCSP service' many times. It is believed that repeated connections caused a time-out.
Apple hasn't announced that the issue was due to an update to Big Sur, but reports from multiple users suggest that the issue has been resolved at the time of writing. IT news site Ars Technica is asking Apple for comment, but it seems that there is no comment at the time of writing the article.
in Software, Posted by darkhorse_log