-
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
Fix and test secp224k1 in PSA code #3541
Comments
#3727 raises a related issue with Curve25519 (255-bit according to PSA, 256-bit according to Mbed TLS). |
Filed as Mbed-TLS#3541. In the meantime, disable the feature. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
Filed as Mbed-TLS#3541. In the meantime, disable the ssl-opt.sh test case that uses it. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
Filed as #3541. In the meantime, disable the feature. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
Filed as #3541. In the meantime, disable the ssl-opt.sh test case that uses it. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
secp224k1 is very rarely used, and we plan to remove it (alongside all curves that are under 255 bits) in the next major version of Mbed TLS. As a consequence, I am keeping this issue open to document the bug, but it is very low priority so we'll probably never get around to fixing it. |
secp224k1 will be removed in the next major release (TF-PSA-Crypto 1.0), and there will not be another feature release. So we are never going to fix secp224k1 in PSA. |
The curve secp224k1 has 225-bit private keys and 224-bit public key coordinates. The PSA code was initially written under the assumption that the size of private keys and public keys is the same, which is true for all the curves supported by Mbed TLS except for secp224k1.
Goals of this task:
The text was updated successfully, but these errors were encountered: