-
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
Declare p256-m as ready for production #8203
Declare p256-m as ready for production #8203
Conversation
Add some guidance as to whether and how to enable it. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
@d3zd3z Please review to indicate your approval of p256-m as a whole. |
(You need extra steps if you want to disable the built-in implementation of ECC algorithms, which includes more features than p256-m. Refer to the documentation of `MBEDTLS_P256M_EXAMPLE_DRIVER_ENABLED` for more information.) | ||
|
||
The driver prefix for p256-m is `P256`/`p256`. | ||
The p256-m driver implements four entry points: `generate_key`, `key_agreement`, `sign_hash`, `verify_hash`. |
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.
Note: #8041 adds the key management entry points. Depending on which one (of this PR and 8041) gets merged first, the other one will need updating.
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
There was a bit of a race condition between Mbed-TLS#8041 which introduced the new entry points, and Mbed-TLS#8203 which documented the list of entry points. Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
There was a bit of a race condition between Mbed-TLS#8041 which introduced the new entry points, and Mbed-TLS#8203 which documented the list of entry points. Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
There was a bit of a race condition between Mbed-TLS#8041 which introduced the new entry points, and Mbed-TLS#8203 which documented the list of entry points. Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
I approve of the p256-m code. This is probably the cleanest and most readable crypto code I've encountered. |
There was a bit of a race condition between Mbed-TLS#8041 which introduced the new entry points, and Mbed-TLS#8203 which documented the list of entry points. Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
There was a bit of a race condition between Mbed-TLS#8041 which introduced the new entry points, and Mbed-TLS#8203 which documented the list of entry points. Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
There was a bit of a race condition between Mbed-TLS#8041 which introduced the new entry points, and Mbed-TLS#8203 which documented the list of entry points. Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
There was a bit of a race condition between Mbed-TLS#8041 which introduced the new entry points, and Mbed-TLS#8203 which documented the list of entry points. Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
I have reviewed the p256-m implementation and integration. The conclusion of my review is:
MBEDTLS_P256M_EXAMPLE_DRIVER_ENABLED
is not a good name for a production feature. Filed as Rename MBEDTLS_P256M_EXAMPLE_DRIVER_ENABLED #8202.PR checklist
Note: Will need rebasing if #8041 gets merged first, see #8203 (comment)