1995-11-30 - Re: Attribute-testimony example (was Re: The future will be easy touse)

Header Data

From: “E. ALLEN SMITH” <EALLENSMITH@ocelot.Rutgers.EDU>
To: cme@TIS.COM
Message Hash: 5a91f679b7bfca267d68da556ce9782879d8668ec7fc4d40240769d81fbbb317
Message ID: <01HY987RZFD48WYZNO@mbcl.rutgers.edu>
Reply To: N/A
UTC Datetime: 1995-11-30 19:27:38 UTC
Raw Date: Fri, 1 Dec 1995 03:27:38 +0800

Raw message

From: "E. ALLEN SMITH" <EALLENSMITH@ocelot.Rutgers.EDU>
Date: Fri, 1 Dec 1995 03:27:38 +0800
To: cme@TIS.COM
Subject: Re: Attribute-testimony example (was Re: The future will be easy touse)
Message-ID: <01HY987RZFD48WYZNO@mbcl.rutgers.edu>
MIME-Version: 1.0
Content-Type: text/plain


From:	IN%"cme@TIS.COM"  "Carl Ellison" 30-NOV-1995 12:34:35.18

Once an element of that set is identified, it can be assigned a codeword
(to make parsing easier).
----------
	How about an email address? Or a URL? Those can be autodetected easily
enough. Plus, the email one could be used to automatically use the
appropriate key if reading something from a particular address (whether for
decryption or for signature verification). If there are more than one with
that address, try all of them and if one turns up looking right (looks like
email headers, for instance) use that decryption. That last is even easier with
the signature verification, and that can show up the user-specified portion of
the field so as to remind you who's sent the message. Sorry if this has been
thought of (and suggested) before... it is kind of obvious.
	-Allen





Thread