GPG - Invalid packet

Harper, Jason (GE Consumer Finance) jason.harper at
Fri Apr 2 16:56:41 CEST 2004


Here is the list-packets on the file that made up the first sample:

gpg --list-packets CE_Con_1040326.dat
gpg: WARNING: using insecure memory!
gpg: please see for more information
:marker packet:
 50 47 50
:pubkey enc packet: version 3, algo 16, keyid xxxxxxxxxxxxxxxxx
        data: [3072 bits]
        data: [3071 bits]
:pubkey enc packet: version 3, algo 16, keyid xxxxxxxxxxxxxxxxx
        data: [1019 bits]
        data: [1023 bits]
:encrypted data packet:
        length: 1549
gpg: encrypted with 3072-bit ELG-E key, ID xxxxxxxxx, created 2001-08-23
      "Company <person at>"
gpg: encrypted with 1024-bit ELG-E key, ID xxxxxxxx, created 2004-03-25
      "Company2 (Company2 decription key) <company2 at>"
:compressed packet: algo=1
:onepass_sig packet: keyid xxxxxxxxxxxxxxxxxxx
        version 3, sigclass 00, digest 2, pubkey 17, last=1
:literal data packet:
        mode b, created 0, name="datadump20040109.dat",
        raw data: 0 bytes
gpg: WARNING: message was not integrity protected

The input files, prior to encyrption, are textual dumps of data.  The CE
file here, when we get it is 27kb.

-----Original Message-----
From: gnupg-users-bounces at
[mailto:gnupg-users-bounces at] On Behalf Of David Shaw
Sent: Friday, April 02, 2004 9:29 AM
To: gnupg-users at
Subject: Re: GPG - Invalid packet

On Fri, Apr 02, 2004 at 08:56:10AM -0500, Harper, Jason (GE Consumer
Finance) wrote:

> I've been using gpg to do file encryption with partners of ours, but 
> we just ran into two odd issues:
> 1. a GPG "don't know: invalid packet (ctb-1f) & (ctb-40) 2. a GPG 
> "problem reading source"
> I've done the google thing on this, but I'm not making much progress.
> Does the list have any pointers for me to look at? We've not run into 
> this before.
> The source file is being encrypted, and compressed and signed by an 
> 7.11 Business PGP system, and we are opening on a Solaris 8 box with 
> gpg 1.2.3.  I've sanitized some of the data to protect the innocent..

Could you run 'gpg --list-packets' on those files?  It might shed some

How large are the files (both input, and expected output sizes) ?

Are the input files ASCII armor ("---BEGIN PGP MESSAGE---", etc) or


Gnupg-users mailing list
Gnupg-users at

More information about the Gnupg-users mailing list