-
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
Remove support for domain parameters #6495
Labels
component-crypto
Crypto primitives and low-level interfaces
enhancement
size-optimisation
size-s
Estimated task size: small (~2d)
Comments
FFDH is deprecated IIUC. |
My understanding is that only FFDH with custom domain parameters (as is done in TLS 1.2) is deprecated, but FFDH with well-known groups (as done in TLS 1.3) is still considered OK (except for the high resource usage compared to ECDH of course) AFAIK. So, pretty consistent with the goal of this issue. |
3 tasks
3 tasks
This was referenced Feb 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
component-crypto
Crypto primitives and low-level interfaces
enhancement
size-optimisation
size-s
Estimated task size: small (~2d)
Domain parameters are an experimental feature which is:
psa_get_key_attributes
, get the public exponent. This is not useful since you can get it from the public key and you basically never need it separately.At this point, it's unlikely that we'll ever implement custom groups for FFDH. We won't implement FFDSA. So we don't really have a planned use for domain parameters. They might come up again with other algorithms (e.g. for PQC, depending on exactly standardization goes), but it's not a given and if they do a different design might work better.
For RSA, the use of domain parameters was grafted on: we needed a way to select a custom public exponent when generating a key, the key attributes were the only way to pass information, and there was this field in the attributes that wasn't used for anything else and kind of fit. If we remove domain parameters, we need a different way to specify the public exponent when generating an RSA key.
Goal of this task: remove support for domain parameters from the API. Prerequisite: implement the alternative method for RSA generation (#8815), and get to a point where we're comfortable with removing support for the old method. Once that's done, the domain parameter functions will be just stubs that do nothing.
Definition of done: domain parameters are removed from the public interface. If they are still present internally, file a follow-up task to clean up.
Advantages:
The text was updated successfully, but these errors were encountered: