From: sdw@sdwsys.lig.net (Stephen D. Williams)
To: eric@parallax.com (Eric Messick)
Message Hash: 635147d87091bbc8aa1303cc2897239732af441cdfe82cc236b166f1bde58e1e
Message ID: <9212241403.AA26014@sdwsys.lig.net>
Reply To: <9212232303.AA26569@parallax.com>
UTC Datetime: 1992-12-24 14:09:09 UTC
Raw Date: Thu, 24 Dec 92 06:09:09 PST
From: sdw@sdwsys.lig.net (Stephen D. Williams)
Date: Thu, 24 Dec 92 06:09:09 PST
To: eric@parallax.com (Eric Messick)
Subject: Re: Signing ascii text
In-Reply-To: <9212232303.AA26569@parallax.com>
Message-ID: <9212241403.AA26014@sdwsys.lig.net>
MIME-Version: 1.0
Content-Type: text/plain
...
>
> The important part here is that the collapsing of whitespace would
> only affect the message digest, not the text as seen by the user. Two
> texts which read the same, but differ in whitespace, would have the
> same signature. If you recieved both files, you could see the
> difference in spacing, yet the same signature would be valid for both
> files. The main vulnerability is that a message whose meaning is
> partially encoded it its whitespace (like an ascii graphic, map, or
> chart) could have its meaning altered, without affecting the validity
> of the signature. Clearly one would not want to use this signature
> method on such texts. It would be a good feature for the signature
> algorithm to warn the user if it detects a pattern of whitespace that
> might convey information. I am not sure how to detect this reliably,
> though.
How about two signatures, verbatim and space-collapsed.
That way if the latter was valid but the former was not, you would
know that spacing was altered but other info remained valid.
sdw
Return to December 1992
Return to “sdw@sdwsys.lig.net (Stephen D. Williams)”