Adds support AES decryption #579
Open
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
Ph0tonic
reviewed
Apr 27, 2024
lib/zip/crypto/aes_encryption.rb
Outdated
| end | ||
|
|
||
| def gp_flags | ||
| 0 |
There was a problem hiding this comment.
As described below, the general purpose flag should be set to 1:
As for any encrypted file, bit 0 of the "general purpose bit flags" field must be set to 1 in each AES-encrypted file's local header and central directory entry.
Suggested change
| 0 | |
| 1 |
| amount_to_read -= BLOCK_SIZE | ||
| @counter += 1 | ||
| end | ||
|
|
There was a problem hiding this comment.
We are missing the check of the CRC, we should check that the decrypted content hasn't been tampered.
There was a problem hiding this comment.
I've tried to integrate the AES integrity check, but it doesn't work.
If you have an idea, I'd love to hear it.
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.
#573 #179 @Ph0tonic