Skip to content
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

Feature request: AES encryption and decryption should support no padding mode #567

Closed
jeffli678 opened this issue May 31, 2019 · 3 comments

Comments

@jeffli678
Copy link

I get some ciphertext encrypted with AES but has no padding. I tried to decrypt it in CyberChef but fails. I think there are two possible improvements:

  1. When an operation fails, give more information on the failure rather than simply say the decryption fails. As for this case, after some research, I found the problem is the CyberChef assumes the ciphertext comes with PKCS 7 padding. However, my input does not have any padding, so it fails. Had CyberChef been able to tell me about this, I would have figured out the problem earlier. See also Bug report: AES Encryption with cipher text of null string appended? #392

  2. Allow the user to select whether or not to use padding.

@Storms-Engineering
Copy link
Contributor

Doing some research on how to specify what padding to use in node-forge

@Storms-Engineering
Copy link
Contributor

I believe I got it working. But I am trying to fix the tests that it broke since I added a new parameter to the config of AES encrypt/decrypt.

@n1474335
Copy link
Member

NoPadding options have been added for CBC and ECB modes in AES, DES and Triple DES Decrypt operations in v9.37.0 #1189

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

No branches or pull requests

3 participants