Live data from Hacker News

Does Apple really log every app you run? A technical look

blog.jacopo.io

151–160 of 355 posts

Re: Does Apple really log every app you run? A technical look

#152
post #127

Apple has always been a gated community, but now there’s a guard at the gate checking everything that goes in and out. This is something most users probably don’t want. It has me personally considering what a future without Apple would look like.

I’m more and more convinced that I’ve got to learn and find a way to make Linux work for me.

They’re not mutually exclusive. I have several macs and several linux machines. One of the linux machines (my router) even keeps the macs safe and (relatively) trustworthy.

It’s a good thing to do regardless. I also know way more than I want to about Windows, too, and could make do if given only that for a workweek.

Learn languages, learn OSes, learn architectures. Get more computers. :)

Re: Does Apple really log every app you run? A technical look

#153
post #145

“It doesn’t send a hash of the app, it sends a thing that is a encoded hash that uniquely identifies the app! Totally different!” It wasn’t a misunderstanding, it was a simplification so that people could understand the issue without me explaining OCSP and app signing and x509 and the PKI. Dozens of people wrote me to thank me for explaining it in a way that they could understand. It is indeed a hash, and it does ind…

Your text was understood that way because of something in the words you chose, maybe "hash of the application" for example.

Re: Does Apple really log every app you run? A technical look

#154

There will be a day when all apps on a mac will only be installable from the app store. Developers will be forced to buy macs and subscribe to Apple’s developer program to support it. Customers will be trained to not care. And HN Apple fanboys and fangirls will try to justify why this is a Good Thing(TM).

We’ve been hearing that for years, yet it hasn’t happened. Apple seems to recognize the value of the Mac as an general computing platform.

Apple has programmed macOS to make it appear to users as if un-Notarized apps either don't work or are malicious.

This is bad for users that download apps to solve problems, or to get work done, because then they can't those apps without having an expert tell them what the magic ritual to run un-Notarized apps is. If they don't have an expert around to show them how to perform the magic ritual, then they just think the apps are broken.

Re: Does Apple really log every app you run? A technical look

#155
post #123

Earlier quoted context omitted.

We’ve been hearing that for years, yet it hasn’t happened. Apple seems to recognize the value of the Mac as an general computing platform.

They’ll never do it. They just keep making stuff not private so you have to choose between security versus privacy. A well thought system would be able to provide both.

They'll do it, it's only a matter of time

Re: Does Apple really log every app you run? A technical look

#157
post #59

Earlier quoted context omitted.

> There is no information on how often the validation happens. I wrote a blog post about this. My analysis indicates that Developer ID OCSP responses were previously cached for 5 minutes, but Apple changed it to half a day after Thursday's outage, probably to reduce traffic: https://lapcatsoftware.com/articles/ocsp.html

5 minutes is an absurdly short cache time…

If you catch malware in the wild you don’t want to wait half a day for the cache to expire.

Negative responses are typically cached for short periods of time. Can you imagine if people cached NXDOMAIN for half a day and someone creating a record had to wait 12 hours for it to go live because someone queried it?

Re: Does Apple really log every app you run? A technical look

#158
post #3

Earlier quoted context omitted.

Did you even read the article? It clearly shows that all that's being sent to Apple is some opaque info about the dev certificate used for the app(s).

Which is still sufficient information to narrow down to the set of applications developed by a single entity. And because this is being done over HTTP, anyone along the network chain has visibility as well.

Agreed, this should be sent encrypted, obviously. My point was that the intent here might not be to "snoop" on users, as even the author points out by comparing his analysis with what Jeffrey Paul's article reported ("[...] that’s quite an important difference on a privacy perspective") but likely to efficiently handle certificate revocation. Hopefully they will find a better way.

Re: Does Apple really log every app you run? A technical look

#159

Earlier quoted context omitted.

Most "alarmist" articles have two points you cannot really ignore, not if you don't want to end up living in interesting times one day. 1) Even plain access logs — basically what a HTTP request, or a TCP connection can tell you — is a lot . Gather those for a couple of days, and you have a good map of the user. More so if you have an ID of machine and the actual executable hash. 2) "But we are the good guys" is a non…

There is no executable hash in the request, so I don't understand why you bring it up

Developer certificate IDs are almost a 1:1 match with which app you’re running.

Re: Does Apple really log every app you run? A technical look

#160

Earlier quoted context omitted.

Wait. Is it not common knowledge that Android and iOS log every application you open down to the exact millisecond you open and close them? Is it not common knowledge how telemetry works for the operating systems? They generally batch up a bunch of logs like this, encrypt them, compress them, and then send them to the mothership (hopefully when you're on WiFi).

first compressed and then encrypted. A good encryption is indistinguishable from random data.

That's why it's compressed before encryption?
Post reply on HN