From: wcs@anchor.ho.att.com (Bill Stewart +1-908-949-0705 wcs@anchor.ho.att.com)
To: cypherpunks@toad.com
Message Hash: a387c1945cfe9f535b4963568f1efa1822ba8b2d2599aea54f1cb27bf24fe1bd
Message ID: <9212232331.AA20426@anchor.ho.att.com>
Reply To: N/A
UTC Datetime: 1992-12-23 23:31:40 UTC
Raw Date: Wed, 23 Dec 92 15:31:40 PST
From: wcs@anchor.ho.att.com (Bill Stewart +1-908-949-0705 wcs@anchor.ho.att.com)
Date: Wed, 23 Dec 92 15:31:40 PST
To: cypherpunks@toad.com
Subject: Re: Signing ascii text
Message-ID: <9212232331.AA20426@anchor.ho.att.com>
MIME-Version: 1.0
Content-Type: text
The problem with signing whitespace-compressed canonicalized text isn't the
loss of readability, since you can send the non-canonicalized version for humans.
The problem is that sometimes the white space IS significant
Project-Schedule 1992 1993 1994
Phase 1 X
Phase 2 X
Phase 3 X
would acquire the same signature if you moved the Xs to different columns.
If we're going to treat white space in text as significant, we made need
to adopt a scheme such as MIME's =xx content-transfer-ncodings;
Otherwise we need to declare by fiat that white space is not significant
unless protected by an encoding.
Bill Stewart
Return to December 1992
Return to “wcs@anchor.ho.att.com (Bill Stewart +1-908-949-0705 wcs@anchor.ho.att.com)”
1992-12-23 (Wed, 23 Dec 92 15:31:40 PST) - Re: Signing ascii text - wcs@anchor.ho.att.com (Bill Stewart +1-908-949-0705 wcs@anchor.ho.att.com)