Don

Summary: Trail of Bits examines what happens when threshold signature schemes, a form of multi-party computation, run inside trusted execution environments, and finds that a malicious host can roll back the filesystem after a signer deletes a used pre-signature, causing nonce share reuse and disclosure of the private key share. The post also catalogs recurring audit pitfalls, including incomplete attestation measurements, missing verification steps, unhardened enclave images, and stale backups served from outside the trust boundary, citing a WhatsApp Private Inference flaw where configuration files were left out of attestation and LD_PRELOAD could inject malicious shared libraries while the quote stayed valid.
What you should know: A single reused pre-signature leaks a signer's private key share, and the rollback that causes it comes from the host your TEE was supposed to defend against, not from a broken protocol. If your attestation quote is valid but measures an incomplete picture, you have cryptographic assurance of the wrong thing.

Read the original at Trail of Bits Blog ↗