1992-12-24 - Signing ascii text
Header Data
From: Bill Sommerfeld <sommerfeld@orchard.medford.ma.us>
To: sdw@sdwsys.lig.net
Message Hash: 86e349f79ee033e5fa74914e8fb1b07284bb3ce07bf0a4d673d63bc0b7eee64e
Message ID: <9212241705.AA00221@orchard.medford.ma.us>
Reply To: <9212241403.AA26014@sdwsys.lig.net>
UTC Datetime: 1992-12-24 17:57:49 UTC
Raw Date: Thu, 24 Dec 92 09:57:49 PST
Raw message
From: Bill Sommerfeld <sommerfeld@orchard.medford.ma.us>
Date: Thu, 24 Dec 92 09:57:49 PST
To: sdw@sdwsys.lig.net
Subject: Signing ascii text
In-Reply-To: <9212241403.AA26014@sdwsys.lig.net>
Message-ID: <9212241705.AA00221@orchard.medford.ma.us>
MIME-Version: 1.0
Content-Type: text/plain
I don't think space-collapsed signatures make any sense; they're only
going to mess up
If you're going to do any canonicalization, do either exactly what PEM
does, or canonicalize tabs and trailing spaces out of the message at
posting time. Then do the same canonicalization on the receive end
before the signature is verified.
If a message transfer path is still "lossy", stop using the unencoded
body and just live with radix64 encoding.
- Bill
Thread
Return to December 1992
- Return to “Bill Sommerfeld <sommerfeld@orchard.medford.ma.us>”
- Return to “Eric Messick <eric@parallax.com>”
Return to “sdw@sdwsys.lig.net (Stephen D. Williams)”
- 1992-12-24 (Wed, 23 Dec 92 19:01:52 PST) - Re: Signing ascii text - Eric Messick <eric@parallax.com>
- 1992-12-24 (Thu, 24 Dec 92 06:09:09 PST) - Re: Signing ascii text - sdw@sdwsys.lig.net (Stephen D. Williams)
- 1992-12-24 (Thu, 24 Dec 92 09:57:49 PST) - Signing ascii text - Bill Sommerfeld <sommerfeld@orchard.medford.ma.us>
- 1992-12-24 (Thu, 24 Dec 92 06:09:09 PST) - Re: Signing ascii text - sdw@sdwsys.lig.net (Stephen D. Williams)