GPG - Invalid packet

Jim Hendrick jrhendri at maine.rr.com
Fri Apr 2 16:19:37 CEST 2004


do you know if it was encrypted with ascii-armor?

I have seen problems with non-ascii systems sending files with wierd
characters.

Jim


> -----Original Message-----
> From: gnupg-users-bounces at gnupg.org
> [mailto:gnupg-users-bounces at gnupg.org]On Behalf Of Harper, Jason (GE
> Consumer Finance)
> Sent: Friday, April 02, 2004 8:56 AM
> To: gnupg-users at gnupg.org
> Subject: GPG - Invalid packet
> 
> 
> <<my deepest apologies if this got posted twice. I was [for 
> some reason]
> not subscribed on the correct e-mail address to post the first time>> 
> 
> Dear Group,
> 
> 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 NAI
> 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..
> 
> Sample one:
> 
> gpg --output ce331 --decrypt CE_Con_1040326.dat
> gpg: WARNING: using insecure memory!
> gpg: please see http://www.gnupg.org/faq.html for more information
> gpg: encrypted with 3072-bit ELG-E key, ID xxxxxxxx, created 
> 2001-08-23
>       "KEYNAME <key at mycorp.com>"
> gpg: encrypted with 1024-bit ELG-E key, ID xxxxxxxx, created 
> 2004-03-25
>       "key at sample.com (COMPANY decription key) <key at sample.com>"
> gpg: Signature made Fri Mar 26 14:20:29 2004 EST using DSA key ID
> xxxxxxxx
> gpg: Good signature from "COMPANY <key at sample.com>"
> gpg:                 aka "COMPANY <key at sample.com>"
> gpg: [don't know]: invalid packet (ctb=1f)
> gpg: WARNING: message was not integrity protected
> gpg: [don't know]: invalid packet (ctb=40)
>  
> Then it just ends, but we end up with a plain text file. 
> Accuracy of the
> file is unkown.  What is the CTB=1f and CTB=40
> 
> Sample two:
> 
> ->> gpg --output au331 --decrypt  AU_Con_1040331.dat
> gpg: WARNING: using insecure memory!
> gpg: please see http://www.gnupg.org/faq.html for more information
> gpg: encrypted with 3072-bit ELG-E key, ID xxxxxxxx, created 
> 2001-08-23
>       "COMPANY <key at mycorp.com>"
> gpg: encrypted with 1024-bit ELG-E key, ID xxxxxxxx, created 
> 2004-03-25
>       "key at sample.com (COMPANY decription key) <key at sample.com>"
> gpg: Signature made Fri Mar 26 14:20:46 2004 EST using DSA key ID
> xxxxxxx
> gpg: Good signature from "COMPANY <key at sample.com>"
> gpg:                 aka "COMPANY <key at sample.com>"
> File `au331' exists. Overwrite (y/N)? yes
> gpg: Problem reading source (2386467048 bytes remaining)
> gpg: handle plaintext failed: file read error
> gpg: WARNING: message was not integrity protected
> 
> Thanks for any and all assistance.
> 
> jason
> 
> 
> _______________________________________________
> Gnupg-users mailing list
> Gnupg-users at gnupg.org
> http://lists.gnupg.org/mailman/listinfo/gnupg-users
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 3620 bytes
Desc: not available
Url : /pipermail/attachments/20040402/cafa57d3/winmail-0001.bin


More information about the Gnupg-users mailing list