-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable Curve448 support via the PSA API #4626
Enable Curve448 support via the PSA API #4626
Conversation
mbedtls_ecp_read_key and mbedtls_ecp_write_key are updated to include support for Curve448 as prescribed by RFC 7748 §5. Test suites have been updated to validate curve448 under Montgomery curves. Signed-off-by: Archana <[email protected]>
Enable Curve448 support Add test vectors to evaluate * RFC 7748 * a known-answer public key export test. * a known-answer ECDH (X448) test. Signed-off-by: Archana <[email protected]>
Signed-off-by: Archana <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think having a changelog file would be good here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That looks almost good to me, thanks. I have only minor comments. I would also suggest to add a "PSA generate key: ECC, Curve448, good" test similar to the "PSA generate key: ECC, Curve25519, good" one to complete the alignment of curve 25519 and curve 448 testing in test_suite_psa_crypto. Otherwise, the PR needs rebasing now.
Improve the description of some curve 448 tests Signed-off-by: Archana <[email protected]>
* Add tests to validate MSB not ok for Curve25519 and Curve448. * Add a test to generate key for for Curve448. Signed-off-by: Archana <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for addressing my comments so quickly. There are a few things that we use to do differently though:
- when a PR is in review and it has some conflicts with the branch it is targeted to we prefer to rebase the PR rather than merge the targeted branch (development in the case of this PR). Thus, could you please remove the last merge commit and rather rebase the PR commits on top of the
development
branch. Feel free to ask if you have some doubt on how to do that. - concerning review conversation we let the reviewer not the PR author resolve the conversations. The PR author usually just uses the rocket icon to indicate to the reviewer that a comment has been addressed.
- when you create new commits to address review comments please make commit message that explain what the commit does and group in one commit similar changes. For example, here a possibility is to have one commit to address the style issues with a commit message like "Fix coding style issue" (it would a squash of your three "Update library/ecp.c" commits. Then we could have one commit "test: psa: Improve the description of some curve 448 tests" ...
Signed-off-by: Archana <[email protected]>
7091628
to
a8605bb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the changes. Almost good to me, please my last comments below.
Signed-off-by: Archana <[email protected]>
a8605bb
to
96d4572
Compare
Signed-off-by: Archana <[email protected]>
96d4572
to
6a66e02
Compare
Signed-off-by: Archana <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the changes. You have some trailing spaces in the change log and the CI is not happy. Otherwise LGTM.
6a66e02
to
554e64e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks.
Description
Enabled Curve448 support via the PSA API fixing #4249.
Added missing support for validating Curve448 keys fixing #3399.
Status
READY
Requires Backporting
NO
Migrations
NO
Todos