CCF
CCF copied to clipboard
microsoft
Confidential Consortium Framework
`set_claims_digest` expects a SHA-256 hash as input, but there is no error check on the size. It accepts value of any size.
As per [Table 21](https://www.amd.com/system/files/TechDocs/56860.pdf), we should also verify additional fields in the attestation report for SEV-SNP. In particular, the `GUEST_POLICY` field (table 8) and the debug, migrate and SMT flags...
Using Azure container instances directly for our CI is simple but we lose a lot of the benefits of hosted pools that we use for the rest of our testing....
We currently verify that a measurement, which is a digest of the UVM, matches exactly a known good measurement. Since UVM updates can happen outside of the users control, this...
Now that we have support for gRPC at the application level, the framework should also support gRPC to report consistent errors to clients. For example, currently, if a gRPC application...
Follow-up to #4157, as this missed the remaining tricky bit: Once we've stolen the `Tx` so it could be used by future requests, how do we: `(a)` mark this user...
The current KV service definition makes each action a discrete, standalone RPC. This is a 1:1 mapping with the existing native API, but is unnecessarily inefficient for a lot of...
We should ensure the `Executor` is able to run standalone in a SEV-SNP container and communicate over gRPC with a CCF node. This may be achieved in the CI, but...
This would allow the operator to present a unified log of governance errors, otherwise reported in individual responses to the relevant members, which may be useful for an auditor or...