invalid packet (ctb=2d)

Sjokotof sjokotof2004 at
Wed Oct 13 10:52:53 CEST 2004

David Shaw <dshaw <at>> writes:

> On Fri, Oct 08, 2004 at 11:05:17AM +0000, Sjokotof wrote:
> > Situation:
> > - production system Win32 running PGP 6.5.8, daily decrypting a series of 
> > incoming files.
> > - trial setup Win 32 running GnuPG 1.2.5, decrypting the same series of 
> > files.
> > - Trial ran OK for months, with the exception of a few days ago, when one 
> > of the files choked GnuPG, but ran fine through GPG.
> Very often, this error:
> > gpg: [don't know]: invalid packet (ctb=2d)
> means that the file is corrupt.  A common way of corrupting files is
> to FTP them in ASCII mode instead of BINARY.  How are your files being
> moved around?

I use wget over FTP, which defaults to Binary mode.
The files begin with -----BEGIN PGP MESSAGE-----, end with -----END PGP MESSAGE-
Would ASCII mode be better in this case?

> I understand that you successfully read this file with PGP, but which
> copy did you test with?  The same one on the same box as GnuPG?

You're right, I used the file's copy which is not the right thing to do when 
troubleshooting. However, GnuPG rejects the copy, too. To make sure, I've 
retested, by having PGP decrypt the file that's on the GnuPG box, working  
directly from the PGP box, reading the fil on the GnuPG box. Again, PGP works 
I was hoping I only had to use some special switch on the commandline to get GPG 
to work...


More information about the Gnupg-users mailing list