|
|
|
|
|
by epcoa
1059 days ago
|
|
> Then they should read the leaked government documents from around the world that contradict what Apple says themselves. On what specifically? > they should at least be able to read the actual code to corroborate its security, but that's not an option either. Why does that matter? You're already trusting Apple hardware. Public access to source code doesn't make security systems safer. I'm not sure what a journalist or even 99% of webshits on this forum would do with trying to audit crypto. |
|
For starters, PRISM and XKeyscore. Both are damning indictments of the state of surveillance a decade ago, and are so damaging that pretty much every FAANG company denies knowledge of their existence. PRISM was about the outreach the US government has with domestic companies, and XKeyscore showed just how far those connections could be abused.
Simply the fact that these leaked documents exist and Apple denying them is a contradiction. Everything else is speculation, but my brain can imagine a lot happening over those past 9 years.
> Why does that matter?
Accountability purposes.
> You're already trusting Apple hardware.
Ideally I don't do that either. I'm not a fan of closed firmware interfaces and if possible, I'd like to audit the code for those as well.
> Public access to source code doesn't make security systems safer.
The majority of networked servers online today beg to differ. Over time the industry actually found that it's much safer to use an open and transparent OS than it is to trust a black-box with UB that may-or-may-not be fixed.
> I'm not sure what a journalist or even 99% of webshits on this forum would do with trying to audit crypto.
This speaks to a lack of either experience or imagination, I can't tell which.