1992-10-14 - Matching Text, Headders and Signatures with Crypto Hashes

Header Data

From: hugh@domingo.teracons.com (Hugh Daniel)
To: cypherpunks@toad.com
Message Hash: 93c22d4a09c05464dc229bf684957f4a4020b1760fd9767649a9dc90fafe3731
Message ID: <9210140150.AA12409@domingo.teracons.com>
Reply To: <9210131710.AA20497@bsu-cs.bsu.edu>
UTC Datetime: 1992-10-14 01:58:39 UTC
Raw Date: Tue, 13 Oct 92 18:58:39 PDT

Raw message

From: hugh@domingo.teracons.com (Hugh Daniel)
Date: Tue, 13 Oct 92 18:58:39 PDT
To: cypherpunks@toad.com
Subject: Matching Text, Headders and Signatures with Crypto Hashes
In-Reply-To: <9210131710.AA20497@bsu-cs.bsu.edu>
Message-ID: <9210140150.AA12409@domingo.teracons.com>
MIME-Version: 1.0
Content-Type: text/plain

  A genral and powerful method of makeing sure that Headders, Bodys
and Signatures match is to use cyrpto-checksums.

  For example in NetNews I proposed changing the MessageId: headder
such that part of the gobldyguk on the left side of the atsign was a
crypto hash of the body of the message and some of the important
sending host generated headders.
  With this system of MessageId:'s anyone who corrupts a message
(intentionaly or otherwise) creates a bogus message, as the next
machine that gets the message can see that the message does not match
it MessageId: line.

  So, if we design the signature system right (with a field for a
crypto hash, or some sort of secondarys signatures to in efect counter
sign various includes such as the plain text) a plain text message can
be signed in such a way that you can be sure that the text is the
right text and none other.
  This can be sent over the airwaves as it is not hideing information
but proveing that it is the right information!

  Systems like this would be *very* usefull right now, are simple to
do (with good advice from Crypto Math types) and usefull to everybody.