Update to use 6.0.0-dev* CCF releases #226
Conversation
There was a problem hiding this comment.
Change of the version needs more, please refer to the recent PR to see what needs to be done #223
Otherwise I do not understand why:
- this was not done on the original branch?
- this requires the change to v6?
More explanation in the PR would be great.
Do you mean on main? I don't think this is ready for main yet, but eventually it's the goal.
Because 6.0.0 is when COSE signatures have been added. They are still in flux, especially until the RFC is finalised, and the change is quite substantial and does not the meet the "security and bug fixes" bar for LTS patches. |
There was a problem hiding this comment.
Since SGX is no longer support in this new CCF release, please make sure to update all the scripts and references where SGX is used as the default platform. There are references that have not been updated in this PR yet (e.g., run_functional_tests.sh, start.sh, build.sh, docker/build.sh, etc.)
|
@andpiccione the SGX cleanup is not blocking 6.0.0 compatibility, or SCITT compliance, so I have ticketed it as #226. My goal on this branch is only to achieve SCITT compliance. |
achamayou
merged commit 2fa69f3
into
microsoft:users/achamayou/cose-receipts
The goal of this PR to set up a branch that uses the latest ccf-6.0.0 dev build (dev2).
The eventual goal is to get scitt-ccf-ledger to serve statements that are fully compliant with https://datatracker.ietf.org/doc/draft-ietf-scitt-architecture/09/.