Skip to content

Conversation

Refizul
Copy link

@Refizul Refizul commented May 12, 2025

Switched use_pkcs1_padding to use_pkcs1_oaep_padding to be compatible with the new version of Crypt::OpenSSL::RSA

FIXES #102

Switched use_pkcs1_padding to use_pkcs1_oaep_padding to be compatible with the new version of Crypt::OpenSSL::RSA
Copy link

@sadt sadt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As someone said in issue's comments, it would be better to completely suppress the line and let the crypto library choose the default padding (which now is oaep anyway).
This would avoid the same problem arising again and again each time a padding mode becomes insecure.

ajmetz added a commit to ajmetz/Crypt-LE that referenced this pull request Sep 30, 2025
[ 30/SEP/2025 AJMETZ ] - commented out line 674 ( $key->use_pkcs1_padding; ) following advice expressed 
in discussion of Git Issue 102 [ do-know#102 ] 
and feedback on an earlier pull request [ do-know#103 (review) ].
This will effectively delegate to Crypt::OpenSSL::RSA to set a default padding,
and avoid the likes of errors such as: "PKCS#1 1.5 is disabled as it is known to be vulnerable to marvin attacks."
@ajmetz
Copy link

ajmetz commented Sep 30, 2025

Have attempted to implement the feedback via #107

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

PKCS#1 1.5 is disabled as it is known to be vulnerable to marvin attacks

3 participants