Fix encrypt.py #3
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Change from ECB to CBC
|
Thank you for you find! I will definitely keep this in mind for future codes as well! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi @HarbingerOfFire, I've read your code and I've seen a potential security problem. In encrypt.py you use AES, as in Blowfish you use ECB_mode, and I have to tell you that ECB is not secure, it is much better to use CBC_mode, although you can also use GCM_mode.
If you want to check the differences between CBC and GCM I leave you the following link: https://crypto.stackexchange.com/questions/2310/what-is-the-difference-between-cbc-and-gcm-mode