You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to the specification in SECON (section 2.1.4) for 4096 bit RSA-keys the RSAES-OAEP algorithm should be used to encrypt the session key.
Currently the tool uses the algorithm implied by the public key of the encryption certificate which defaults to RSA (PKCS#1 v1.5).
This causes interoperability issues when decrypting messages created with secon-tool using other tools expecting RSAES-OAEP instead of RSA.
The text was updated successfully, but these errors were encountered:
According to the specification in SECON (section 2.1.4) for 4096 bit RSA-keys the RSAES-OAEP algorithm should be used to encrypt the session key.
Currently the tool uses the algorithm implied by the public key of the encryption certificate which defaults to RSA (PKCS#1 v1.5).
This causes interoperability issues when decrypting messages created with secon-tool using other tools expecting RSAES-OAEP instead of RSA.
The text was updated successfully, but these errors were encountered: