davidczech

Isn't the same machine used for milkshakes? That's kind of staple of burger joints.

No, but the binaries executed will be available for download.

The OS build and cryptex binaries aligning to the hashes found in the transparency log will be made available for download. These are reconcilable with attestations signed by the SEP.

The source code provided is for reference to help with disassembly.

Edit link: https://security.apple.com/documentation/private-cloud-compu...

> cannot protect against that because Apple is a "trusted software publisher" in the chain.

That's the whole point of the transparency log. Anything published, and thus to be trusted by client devices, is publicly inspectable.

> It is a supply-chain / MITM protection measure

It is so much more than that, but you are entitled to your own opinion.

> How can anyone verify that all the code paths append to the log? I'm pretty sure they can just not append to the log from their ExfiltrateDataForAdvertisment() and ExfiltrateDataForGovernments() functions.

I think we have different understandings of what the transparency log is utilized for.

The log is used effectively as an append-only hash set of trusted software hashes a PCC node is allowed to run, accomplished using Merkle Trees. The client device (iPhone) uses the log to determine if the software measurements from an attestation should be rejected or not.

https://security.apple.com/documentation/private-cloud-compu...

> they can choose to emit whatever logs they want into the "transparent logs" and then emit whatever else they don't want into non-transparent logs.

The log is publicly accessible and append-only, so such an event would not go un-noticed. Not sure what a non-transparent log is.

Similar, but a lot of documentation is provided, source code for cross reference, and a VM based research environment instead of applying for a physical security research device.

I wish that was true, but the exit and prompt return of seemingly every PC game developer back to Steam doesn't give much hope.

Darn, I remember checking this website everyday for new games when I had the 1st generation iPod Touch.

Neo

I've seen the problem surface in designs where a single key is shared across many devices.

Servers send signed statements describing its state, and clients make the yes/no determination.