what is misleading exactly?
the part where every app you open gets sent to apple along with third parties along with your IP?
because I’m pretty sure that’s all 100% true, and I think its been true for over 5 years…
you’re just suggesting that because they do one thing well they do everything well, which is a fallacy.
Also, any proprietary program that does “E2EE” is misleading you by omitting the part where they could totally steal anyones keys at any time with the push of a button, if they haven’t already. it is completely laughable to suggest any proprietary E2EE program is secure!
so who is spreading the missinfo again?
Dnn@lemmy.world 1 year ago
The video is basically some dude reading a blog post (boy, I hate those, provide no value). The blog post he reads is this: sneak.berlin/20201112/your-computer-isnt-yours/
The author comments to the blog post you linked and it partially makes sense: if you fetch the developer’s certificate, Apple knows when you started an application of that developer (and which public IP address you have).
Whether or not there are many devs that only made one application, so you can identify this, I cannot estimate, I’m not an Apple user. But you don’t need to send a hash calculated in client side to get this info.
octalfudge@lemmy.world 1 year ago
You’re absolutely right that it’s still an issue to transmit information about the developer certificate. Apple published a response to this, which admittedly is not ideal:
support.apple.com/en-us/HT202491#view:~:text=Priv…
We have never combined data from these checks with information about Apple users or their devices. We do not use data from these checks to learn what individual users are launching or running on their devices.
These security checks have never included the user’s Apple ID or the identity of their device. To further protect privacy, we have stopped logging IP addresses associated with Developer ID certificate checks, and we will ensure that any collected IP addresses are removed from logs.
In addition, over the the next year we will introduce several changes to our security checks:
A new encrypted protocol for Developer ID certificate revocation checks
Strong protections against server failure
A new preference for users to opt out of these security protections
Shikadi@wirebase.org 1 year ago
I mean that sounds like a pretty good response to me