1995-01-24 - Re: Shell’s authentication needs

Header Data

From: “L. McCarthy” <lmccarth@ducie.cs.umass.edu>
To: cypherpunks@toad.com (Cypherpunks List)
Message Hash: fa7916bfc3cbd908c7036372109cd4e0fd1579dbea7ad4f2ed3279e8ea14082b
Message ID: <199501242136.QAA02364@ducie.cs.umass.edu>
Reply To: <9501211317.AA00188@sulphur.osf.org>
UTC Datetime: 1995-01-24 21:35:30 UTC
Raw Date: Tue, 24 Jan 95 13:35:30 PST

Raw message

From: "L. McCarthy" <lmccarth@ducie.cs.umass.edu>
Date: Tue, 24 Jan 95 13:35:30 PST
To: cypherpunks@toad.com (Cypherpunks List)
Subject: Re: Shell's authentication needs
In-Reply-To: <9501211317.AA00188@sulphur.osf.org>
Message-ID: <199501242136.QAA02364@ducie.cs.umass.edu>
MIME-Version: 1.0
Content-Type: text/plain


Rich Salz writes:
> Shell needs public key because they want to use email for legal contracts.
> They've been waiting for standards to come around, but have given up.
> They're currently planning on using NIST's DSS, if they can fix a few things:
>     -	Add concepts of time and location (it can be important to prove
> 	that this was signed last month outside of the U.S.)

Any thoughts on how digital "place-stamping" (analogous to timestamping) might
be accomplished, to authenticate the location of origin of a document ?

 -L. McCarthy / seeking a summer job/internship; BS CS Cornell & 2 years'
  grad work in theoretical CS (algebraic algorithms); private email for info




Thread