-
Notifications
You must be signed in to change notification settings - Fork 461
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
add possibility to use different hash algorithms in RSAES-OAEP #612
Conversation
Hi I made the following changed to perl's CryptX module which should be fine but I get: realloc(): invalid next size
|
Ping @karel-m |
067c5e2
to
77a3fcb
Compare
ah, I made a mistake, can you please try again? |
Yes, that was able to decrypt my test |
Just need the encrypt now and I can test that too :-) |
77a3fcb
to
fa543c1
Compare
Can you give it a try? |
fa543c1
to
22ee920
Compare
These changes seem to work fine for me. I tested with the following combinations encrypting with a modified Perl Crypt::PK::RSA and decrypting the keys with xmlsec1 (using openssl library) The data method is just the key used to encrypt the data in my XML files
|
Requires changes from libtom libtom/libtomcrypt#612
Requires changes from libtom libtom/libtomcrypt#612
Requires changes from libtom libtom/libtomcrypt#612
Requires changes from libtom libtom/libtomcrypt#612
@sjaeckel any update/progress? |
22ee920
to
8b6d39e
Compare
Thanks for keeping it fresh :-).
I was going to suggest a separate API call _ex to take a page out of
openSSL's book and you probably don't want to take a page out of openSSL's
book...
But, it's already _ex... :-)
Tim
Timothy Legge
***@***.***
***@***.***
…On Mon, Aug 7, 2023 at 10:49 AM Steffen Jaeckel ***@***.***> wrote:
@sjaeckel <https://github.com/sjaeckel> any update/progress?
not really ... at least I've rebased on current develop.
@karel-m <https://github.com/karel-m> any comments or suggestions how we
could handle the API break a bit better?
—
Reply to this email directly, view it on GitHub
<#612 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAH3N665KPUONKXNQDJ3S6DXUDW43ANCNFSM6AAAAAAVXQ44KA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Requires changes from libtom libtom/libtomcrypt#612
@karel-m could you please have a look at this PR as well? |
1/ I do not like the variable name 2/ We are breaking compatibility of Otherwise looks good. |
@sjaeckel could you please rebase |
Requires changes from libtom libtom/libtomcrypt#612
The hash algorithms used in the MGF and to create the hash of the Label must not forcibly be the same. This change allows to use different algorithms. Unfortunately this breaks the API if you use one of: * `rsa_decrypt_key_ex()` * `rsa_encrypt_key_ex()` * `pkcs_1_oaep_decode()` * `pkcs_1_oaep_encode()` The `rsa_decrypt_key()` and `rsa_encrypt_key()` macros are still the same. Signed-off-by: Steffen Jaeckel <[email protected]>
8b6d39e
to
63091c9
Compare
and |
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.
Looks good, I am for merging.
The hash algorithms used in the MGF and to create the hash of the Label must not forcibly be the same. This change allows to use different algorithms.
Unfortunately this breaks API if you use
rsa_decrypt_key_ex()
. Thersa_decrypt_key()
macro is still the same.Checklist