CCF
CCF copied to clipboard
Confidential Consortium Framework
To provide support for AMD SEV-SNP in ACI, we should add support for retrieval and verification of SEV-SNP attestation reports so that an existing network can verify the measurement of...
We currently have a distinction between different kind of internal CCF governance tables, and application tables (applications can read governance but not write it, even governance can't write internal system...
There's a few issues with our current JSON macros: - Forces conflation of serialisation and deserialisation. A field is either required (always present in serialisations, must be present to deserialise),...
Suggested by @achamayou. **Is your feature request related to a problem? Please describe.** If we have many instances of CCF stacked onto one set of VMs then the leaders may...
**Describe the bug** We missed some files such as 0.pem when using sandbox.sh to start CCF Node. But it worked when we use the same command line to run. Could...
Once #4068 is complete, we should release a separate package and docker image of CCF so that it can be deployed in ACI, without requiring Open Enclave: - [ ]...
Once #4068 is complete, we should create an ACI setup to test the SEV-SNP variant of CCF in the CI. - [x] 1. Add SEV-SNP ACI CI agent (https://github.com/microsoft/CCF/pull/4171) -...
https://github.com/microsoft/CCF/blob/1430f4dc48184ad0002176e2bc8557600299ee9f/samples/apps/logging/logging.cpp#L844-L848 I'm assuming the reason why the historical query adapter is written around `EndpointContext` instead of `ReadOnlyEndpointContext` is to give more flexibility in case something has to written to the...
We ought to have one end to end test that uses IPv6 if we make this explicit claim. _Originally posted by @achamayou in https://github.com/microsoft/CCF/pull/3209#discussion_r751049550_
- [x] 1. Snapshot evidence verification with ledger suffix Reason: snapshots will include receipt from 2.x and all snapshots used to start 3.x nodes have to be 2.x snapshots (see...