### Fixed CRC-32 error when writing to ZipOutputStream #4
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
Added an explicit call to outputStream.closeEntry() after writing the encrypted bytes to ensure proper entry closure and correct CRC-32 validation.
|
Thank you for your contribution! |
Miroshka000
force-pushed
the
fix-crc32-error
branch
from
66fb440
to
0d9b7ec
Compare
Miroshka000
force-pushed
the
fix-crc32-error
branch
from
dbe12a0
to
8eb6e46
Compare
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.
Changes:
ZipEntryto avoid potential data integrity issues.outputStream.closeEntry()after writing the encrypted bytes to ensure proper entry closure and correct CRC-32 validation.These changes ensure that the
encryptFilemethod correctly writes encrypted files to the zip archive, preventing CRC-32 checksum errors.Best regards,
Miroshka