1996-07-04 - Re: Lack of PGP signatures
Header Data
From: David Lesher <wb8foz@nrk.com>
To: alano@teleport.com (Alan Olsen)
Message Hash: f9dc507af669eba677f088331206a8d0f924fc8864f245818fd9025faadae624
Message ID: <199607040145.VAA05041@nrk.com>
Reply To: <2.2.32.19960703220436.00e93fe8@mail.teleport.com>
UTC Datetime: 1996-07-04 04:37:14 UTC
Raw Date: Thu, 4 Jul 1996 12:37:14 +0800
Raw message
From: David Lesher <wb8foz@nrk.com>
Date: Thu, 4 Jul 1996 12:37:14 +0800
To: alano@teleport.com (Alan Olsen)
Subject: Re: Lack of PGP signatures
In-Reply-To: <2.2.32.19960703220436.00e93fe8@mail.teleport.com>
Message-ID: <199607040145.VAA05041@nrk.com>
MIME-Version: 1.0
Content-Type: text
> I am wondering why there is not a signing option that ignores all
> non-printing characters. Might fix some of these problems... (Can anyone
> think of a reason this would be a "Bad Thing(tm)"?)
Moving spaces could change meaning on a legal doc.
A nonsense example is the alt.folklore.urbane "cow orker" tag...
--
A host is a host from coast to coast.................wb8foz@nrk.com
& no one will talk to a host that's close........[v].(301) 56-LINUX
Unless the host (that isn't close).........................pob 1433
is busy, hung or dead....................................20915-1433
Thread
Return to July 1996
- Return to “Alan Olsen <alano@teleport.com>”
- Return to “David Lesher <wb8foz@nrk.com>”
- Return to ““Mark M.” <markm@voicenet.com>”
Return to “snow <snow@smoke.suba.com>”
- 1996-07-04 (Thu, 4 Jul 1996 09:16:18 +0800) - Re: Lack of PGP signatures - Alan Olsen <alano@teleport.com>
- 1996-07-04 (Thu, 4 Jul 1996 12:37:14 +0800) - Re: Lack of PGP signatures - David Lesher <wb8foz@nrk.com>
- 1996-07-04 (Thu, 4 Jul 1996 16:25:07 +0800) - Re: Lack of PGP signatures - snow <snow@smoke.suba.com>
- 1996-07-05 (Fri, 5 Jul 1996 09:21:16 +0800) - Re: Lack of PGP signatures - “Mark M.” <markm@voicenet.com>