header field causing problem

ejonesca at yahoo.com ejonesca at yahoo.com
Sun Sep 21 14:46:36 CEST 2008


Thanks. I'll let the sender know.

By the way, he says it was using Thunberbird with Enigmail to create the message.



--- On Sat, 9/20/08, David Shaw <dshaw at jabberwocky.com> wrote:

> From: David Shaw <dshaw at jabberwocky.com>
> Subject: Re: header field causing problem
> To: gnupg-users at gnupg.org
> Date: Saturday, September 20, 2008, 6:56 PM
> On Sat, Sep 20, 2008 at 02:24:01PM -0700, ejonesca at yahoo.com
> wrote:
> > I got a message that gpg failed to decrypt. It looked
> something like this:
> > 
> >  -----BEGIN PGP MESSAGE-----
> > Charset: ISO-8859-1
> > 
> > Version: GnuPG v1.4.9 (MingW32)
> > Comment: Using GnuPG with Mozilla -
> http://enigmail.mozdev.org
> > 
> > hQQOAx8Jy...
> >  -----END PGP MESSAGE-----
> 
> It looks like the message was slightly corrupt. 
> Specifically, there
> is a blank line after the "Charset" header and
> before the "Version"
> header.  That's an invalid file - there is supposed to
> be only one
> blank line, and it comes right before the base64 data.
> 
> I'm not sure what generated that message.  I know it
> claims to be GPG
> 1.4.9, but GPG doesn't use the Charset header, so at
> least that line
> must have come from elsewhere.
> 
> David
> 
> _______________________________________________
> Gnupg-users mailing list
> Gnupg-users at gnupg.org
> http://lists.gnupg.org/mailman/listinfo/gnupg-users


      



More information about the Gnupg-users mailing list