invalid packet (ctb=2d)

David Shaw dshaw at
Tue Oct 12 23:05:26 CEST 2004

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 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?


More information about the Gnupg-users mailing list