Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

macOS unable to open any non-Apple application

twitter.com

Post reply on HN
Print view View original

51–60 of 1001 posts

Re: macOS unable to open any non-Apple application

#51

Post by cortesoft »

brundolf wrote: post #43
Lammy wrote: post #33

Maybe it's just me but the idea that my computer lets Apple (+ any LE organizations) surveil my app launches seems so much scarier than any malware.

I don't know about you, but hashes of the binaries I run don't exactly reveal any sensitive personal information about me. That said, obviously they should have much more graceful degradation in place for when something is wrong with the service.

It reveals how often I am running new software, it reveals what time of day I run new software, it reveals what networks I connect from

Re: macOS unable to open any non-Apple application

#52

Post by _qulr »

OCSP is Online Certificate Status Protocol. The connection to ocsp.apple.com is checking the status of the certificate used to code sign the launching app.

I wrote an article about this a couple weeks ago because of the temporary revocation of HP's signing cert for printer drivers on the Mac:

https://lapcatsoftware.com/articles/revocation.html

Re: macOS unable to open any non-Apple application

#53

Post by jen20 »

commonturtle wrote: post #6

You should never, ever, install a MacOS update the moment it comes out. There is a high chance (> 30% from my experience) that something will be wrong with it. iOS too for that matter. Wait for at least one week and check out other people's experiences first.

> Wait for at least one week and check out other people's experiences first.

Of course if everyone does this, there is no experience upon which to draw.

Furthermore, the title is straight up wrong: this is not related to Big Sur and is in fact also affecting other versions with Gatekeeper.

Re: macOS unable to open any non-Apple application

#55

Post by Lammy »

brundolf wrote: post #43
Lammy wrote: post #33

Maybe it's just me but the idea that my computer lets Apple (+ any LE organizations) surveil my app launches seems so much scarier than any malware.

I don't know about you, but hashes of the binaries I run don't exactly reveal any sensitive personal information about me. That said, obviously they should have much more graceful degradation in place for when something is wrong with the service.

"Hey Siri, select every Tor Browser user in America for additional screening."

Re: macOS unable to open any non-Apple application

#57

Post by read_if_gay_ »

submeta wrote: post #2

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,…

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.

Re: macOS unable to open any non-Apple application

#58

Post by p1necone »

modeless wrote: post #19

You've got to be kidding me. When Apple's servers are down, all Macs worldwide start freezing randomly? My XCode is hanging during builds, is this why? This code signing enforcement stuff has gone way too far. Heads should roll for this.

Wait what happens if you don't have an internet connection? Can Macs not be used offline any more, surely that's still a relatively common use case for a laptop even today in a lot of places?

Re: macOS unable to open any non-Apple application

#59

Post by jen20 »

dawnerd wrote: post #35
commonturtle wrote: post #6

You should never, ever, install a MacOS update the moment it comes out. There is a high chance (> 30% from my experience) that something will be wrong with it. iOS too for that matter. Wait for at least one week and check out other people's experiences first.

I ran the beta over the summer and it was awful. I loved the changes but it was just unstable as hell. And people kept saying it was the most stable is yet, I don’t get it.

I’ve been running it as a daily driver since the first day of the developer betas and have found it to be vastly more stable than the previous version, with basically no issues before this.

I don’t know what to tell you, beyond the fact that all use cases are not the same, apparently.

Post reply on HN