Re: GNUPG error/problem (690 Views)
Honored Contributor
Posts: 1,291
Registered: ‎06-18-2007
Message 1 of 4 (690 Views)

GNUPG error/problem

My system: BL860c, OpenVMS 8.3-1H1, GNUPG 1.4.7.

We have been using this product successfully for close to 2 years to send bulk invoices (in an encrypted form) to a company that turns them into PDFs, which are then returned to us as an encrypted ZIP file.

For some reason, when the file was returned to us today, the attempt at decryption resulted in

gpg: block_filter 2C9C70: read error (size=4315,a->size=4315)
gpg: block_filter 2C9990: read error (size=4839,a->size=4839)
gpg: [don't know]: invalid packet (ctb=08)
gpg: [don't know]: invalid packet (ctb=19)
gpg: WARNING: message was not integrity protected
gpg: [don't know]: invalid packet (ctb=36)
gpg: block_filter: pending bytes!
gpg: block_filter: pending bytes!
%NONAME-E-NOMSG, Message number 00000002

Can anyone shed any light on what might be causing this?? I don't know anything about the make/model/OS/GNUPG vers at the other end, only that it failed today. Nothing has changed at my end, and I have the other company looking at their end.

I am just looking for as many opinions and comments as possible incase they come up empty.


Honored Contributor
Posts: 5,049
Registered: ‎01-29-2006
Message 2 of 4 (690 Views)

Re: GNUPG error/problem

Try this gpg port in place of the one you're using:

It's a newer port, and it's been more reliable than the one you're probably using.
Honored Contributor
Posts: 1,291
Registered: ‎06-18-2007
Message 3 of 4 (690 Views)

Re: GNUPG error/problem

This is no longer an issue. Our partner fixed their file at their end and we successfully Pulled, Decrypted and UnZipped the file at our end.

(Still curious if anyone can give a link to documentation which explains the error messages associated with GNUPG)


Honored Contributor
Posts: 9,173
Registered: ‎02-23-2005
Message 4 of 4 (690 Views)

Re: GNUPG error/problem

> Try this gpg port [...]

I'd certainly try that, but I haven't seen a
problem like the one you're reporting. It
looks as if it might be a generic I/O error,
so it might be caused by something simple,
like a truncated file.

> [...] an encrypted ZIP file.

A Zipped encrypted (Zip) file might provide
a little more file integrity checking. (Or
at least a more easily recognized symptom.)
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.