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
Support ECDSA private keys for TLS #3069
Comments
Comment from mreynolds (@mreynolds389) at 2019-01-03 17:53:57 Metadata Update from @mreynolds389:
|
Comment from firstyear (@Firstyear) at 2019-01-15 06:20:04 @kenoh We've just had a request for this in 50160, so it would be great if you could look into this soon! Thanks, |
Comment from mhonek (@kenoh) at 2019-01-15 09:46:36 Metadata Update from @kenoh:
|
Comment from mhonek (@kenoh) at 2019-03-06 16:29:08 Metadata Update from @kenoh:
|
Comment from mreynolds (@mreynolds389) at 2020-02-26 16:48:33 Metadata Update from @mreynolds389:
|
Comment from mreynolds (@mreynolds389) at 2020-07-21 18:16:29 Metadata Update from @mreynolds389:
|
Comment from mreynolds (@mreynolds389) at 2020-07-21 18:16:29 Issue linked to Bugzilla: Bug 1859298 |
It sounds like when a user attempts a pure ecdsa key that this can lead to some misleading/vague errors, so we should consider implementing this sooner-than-later. |
Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/50010
Issue Description
Support ECDSA private keys. This is both:
How this looks today is unknown. However, it doesn't work given:
This is important as it blocks us from using strong future proof cryptographic mechanisms in TLS.
This may be of interest to @kenoh.
Important would be establishment of a ECDSA type in the nss_ssl.py module so we can test this properly and programmatically.
The text was updated successfully, but these errors were encountered: