-
-
Notifications
You must be signed in to change notification settings - Fork 772
Add support for openssl3 KDF methods #1426
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
Conversation
b42fec4
to
0b7e667
Compare
Signed-off-by: Arthur Gautier <[email protected]>
Signed-off-by: Arthur Gautier <[email protected]>
Signed-off-by: Arthur Gautier <[email protected]>
Signed-off-by: Arthur Gautier <[email protected]>
Signed-off-by: Arthur Gautier <[email protected]>
Signed-off-by: Arthur Gautier <[email protected]>
From discussion on openssl/openssl#14551 it sounds like set_params is going to be deprecated. Signed-off-by: Arthur Gautier <[email protected]>
Signed-off-by: Arthur Gautier <[email protected]>
f826776
to
41995aa
Compare
Why not send PR based on #1264 |
it's based on openssl-300 and targets it, so I'm not sure what you're referring to. |
@sfackler, you closed this without comment--are you open to adding support for this KDF functionality? |
@jstarks it automatically closed because the target branch has been removed. I did not have time to re-target and make the adjustments necessary. feel free to take over. |
Ah, I see. OK, I may follow up here later. |
This PR tries to add support for the KDF api openssl3 brings.
The current implementation works, but only supports the KDF I need. I'm sharing early see if you'd have any opinions about the proposed API before I add support for other KDFs.
From my understanding, KDF only works with
OSSL_PARAMS
which are not the easiest thing to use from rust. This is an attempt, but I'm not necessarily convinced.Please don't mind the extra OAEP label commit, It's merged in master, it's only here because it's easier for me to develop and test the whole api. I'll drop the commit eventually.