From: Martin Pool <mbp@pharos.com.au>
To: Jim Burnes <jim.burnes@ssds.com>
Message Hash: 4d4a5ac122eb1cd8898b507bd81243dc023eb890681f8a263b8fca0ffe8b0335
Message ID: <Pine.LNX.3.95.970821102312.7946D-100000@buffalo.pharos.com.au>
Reply To: <Pine.LNX.3.95.970820181959.28582G-100000@westsec.denver.ssds.com>
UTC Datetime: 1997-08-21 00:44:46 UTC
Raw Date: Thu, 21 Aug 1997 08:44:46 +0800
From: Martin Pool <mbp@pharos.com.au>
Date: Thu, 21 Aug 1997 08:44:46 +0800
To: Jim Burnes <jim.burnes@ssds.com>
Subject: Re: Bad signature from announce@lp.org
In-Reply-To: <Pine.LNX.3.95.970820181959.28582G-100000@westsec.denver.ssds.com>
Message-ID: <Pine.LNX.3.95.970821102312.7946D-100000@buffalo.pharos.com.au>
MIME-Version: 1.0
Content-Type: text/plain
On Wed, 20 Aug 1997, Jim Burnes wrote:
> > > ------- Forwarded Message Follows -------
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > >
> > > ===============================================
> > > NEWS FROM THE LIBERTARIAN PARTY
> > > 2600 Virginia Avenue, NW, Suite 100
> > > Washington DC 20037
> > > ===============================================
> > [...]
> >
> > On my machine, using keyid 1024/A7406ED1 <announce@lp.org> the signature
> > did not match the message. Most likely there was a harmless alteration in
> > the process of being forwarded, but possibly the message is bogus.
> >
> > Martin Pool
> >
> >
>
> Yes...the "-------- Forwarded Message Follows ------" line.
>
> Unless you already took that into account in which case its
> probably the ">" symbols or something to that effect.
No, the "-------- Forwarded Message Follows ------" line is before the PGP
begin line, so I think it should not corrupt the signature. I can't see
any '>' quotes inside the message. I suppose probably there's an extra
space or newline in there. I'm not 100% sure if PGP collapses
whitespace to avoid this or not... I imagine probably not.
Martin Pool
Return to August 1997
Return to “Tim May <tcmay@got.net>”