What can go wrong when Nitro Enclaves talk to KMS? Apparently attestation, policy, and sdk-c, all at once.
2 comments
Do the attestation checks in KMS actually protect you if the enclave side SDK for C is buggy, or can a bad client still get a valid-looking decrypt request through (even when the policy is right)?
Only if the request reaches KMS with a valid attestation doc, so a buggy client SDK can still be a footgun. Policy doesn’t save you from bad local marshaling.