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

Don't use ECB and PKCS#1V1.5 #67

Open
cryptochecktool opened this issue Nov 16, 2024 · 0 comments
Open

Don't use ECB and PKCS#1V1.5 #67

cryptochecktool opened this issue Nov 16, 2024 · 0 comments

Comments

@cryptochecktool
Copy link

In the project’s encryption implementation, I noticed the use of ECB (Electronic Codebook) mode and PKCS#1 v1.5 padding scheme. Here are my concerns regarding these methods:

Issues with ECB mode:
ECB mode produces the same ciphertext for identical plaintext blocks, leading to risks of pattern recognition and data leakage.
It is not suitable for scenarios where there may be correlation or repetition between encrypted data blocks.
Issues with PKCS#1 v1.5:
PKCS#1 v1.5 padding scheme is vulnerable to timing attacks during the decryption process, which can allow an attacker to deduce information about the padding and potentially decrypt the message without the private key.

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

No branches or pull requests

1 participant