PK architecture and project specification #9555
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
New interface design and overview of required work. The task breakdown has only been done for preliminaries, not for the bulk of the work. Signed-off-by: Gilles Peskine <[email protected]>
gilles-peskine-arm
added
component-crypto
gilles-peskine-arm
added
priority-high
|
I am closing this pull request because we have scaled down our expectations for TF-PSA-Crypto 1.0 and Mbed TLS 4.0, and we will not make radical changes to the pk module. We will instead make minimal changes. In particular, some parts of pk will become private but will still be used in X.509 and TLS as of Mbed TLS 4.0, and those parts will only be replaced and removed later. Parts of this specification are still of interest, but I will make a new specification document in a new pull request for the revised pk project. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New interface design and overview of required work. Resolves #8452 once this is merged and we have filed GitHub issues corresponding to the task breakdown.
I've tried to minimize the amount of changes compared to the current code. This is mostly a cleanup, keeping the 3.6 transition workflows identical where it's sensible to do so, with few new interfaces.
Status: architecture for the original goal of a clean 4.0 mostly complete. Task breakdown only barely started. Needs heavy rework because we have scoped 4.0 down to be minimal changes.
PR checklist