-
Notifications
You must be signed in to change notification settings - Fork 53
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
java.io.EOFException: Unexpected end of ZIP input stream using 2.2.0 version for PGP file #56
Comments
I have a similar, not identical, EOFException with 2.2.0. I had to revert back to previous version to restore production. |
Here's the stacktrace I'm seeing. I put it here, because I think it's the same root cause. If not, let me know and I can open a separate ticket.
EDIT: I see there's already a ticket for this (issue #46), which is fixed. @neuhalje Is there are reason we're not getting a release with the fix? |
The reason is ... $DAYJOB. I have a day of on Friday - will do a release there. |
Fixed in 2.3.0 |
Hello, I'm using the version 2.3.0 and I'm still having the issue.
|
Describe the bug
I'm trying to decrypt a PGP file encrypted with an old version of BC (2017) within bouncy-gpg 2.2.0 and it fails giving me the error
java.io.EOFException: Unexpected end of ZIP input stream
at org.bouncycastle.openpgp.PGPCompressedData$1.fill(Unknown Source)
at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:158)
at org.bouncycastle.bcpg.BCPGInputStream.read(Unknown Source)
at org.bouncycastle.bcpg.BCPGInputStream$PartialInputStream.read(Unknown Source)
at org.bouncycastle.bcpg.BCPGInputStream.read(Unknown Source)
at java.io.InputStream.read(InputStream.java:101)
If I use bouncy-gpg 2.1.2, file is decrypted.
If I use bouncy-gpg 2.1.2 with last version of bcprov-jdk15on 1.65.01 and bcgp-jdk15on 1.65, file is decrypted
If I use bouncy-gpg 2.2.0 with last version of bcprov-jdk15on 1.65.01 and bcgp-jdk15on 1.65, file decryption fails giving me the same issue.
To Reproduce
Expected behavior
Based on my test, I think that the issue is within bouncy-gpg libraries instead of something related to BC libraries.
** System (please complete the following information):**
The text was updated successfully, but these errors were encountered: