Define “taking down”
macOS unable to open any non-Apple application
81–90 of 1001 posts
Re: macOS unable to open any non-Apple application
#82Define “taking down”
Re: macOS unable to open any non-Apple application
#83Define “taking down”
Re: macOS unable to open any non-Apple application
#84Does anybody now how to disable all hashing on macOS? The best I could do was disable GateKeeper with `sudo spctl --master-disable`.
You can also disable code signing enforcement and amfi by adding the following boot args: cs_enforcement_disable=1 amfi_get_out_of_my_way=1
`sudo defaults write /Library/Preferences/com.apple.security.libraryvalidation.plist DisableLibraryValidation -bool true`
Re: macOS unable to open any non-Apple application
#85Re: macOS unable to open any non-Apple application
#86Define “taking down”
Unix workflows like to call hundreds of small programs.
If Apple doesn't respond in time, your system halts.
Re: macOS unable to open any non-Apple application
#87Is it possible that we (the internet) don't understand this properly because by this logic, the apps shouldn't run when there is no internet connection. I don't believe that is the case.
No connection -> Fine Good connection -> Fine Spotty connection -> Problematic. Basically, they didn't include a timeout in their network code.
Re: macOS unable to open any non-Apple application
#88Well, how interesting that Apple's software is going to be bypassing Little Snitch, making it harder to discover and fix this sort of issue.
Re: macOS unable to open any non-Apple application
#89Unbelievable. 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,…