From: Adam Back <aba@dcs.ex.ac.uk>
To: pooh@efga.org
Message Hash: 38ed2b50e97dfc1ee6ab147404e143cf6c043b83cf06629ed8761ccdf4dddd98
Message ID: <199801081450.OAA00500@server.eternity.org>
Reply To: <3.0.3.32.19980108035645.037abe0c@mail.atl.bellsouth.net>
UTC Datetime: 1998-01-08 22:32:29 UTC
Raw Date: Fri, 9 Jan 1998 06:32:29 +0800
From: Adam Back <aba@dcs.ex.ac.uk>
Date: Fri, 9 Jan 1998 06:32:29 +0800
To: pooh@efga.org
Subject: time-stamp server uses (Re: Question on U.S. Postal Service and crypto)
In-Reply-To: <3.0.3.32.19980108035645.037abe0c@mail.atl.bellsouth.net>
Message-ID: <199801081450.OAA00500@server.eternity.org>
MIME-Version: 1.0
Content-Type: text/plain
Robert Costner <pooh@efga.org> writes:
> [...] The timestamping is a action that "postmarks" the digitally
> signed message. Many attorneys feel this is a very good thing,
> though I have had a hard time justifying the need for this to some
> technically inclined people.
One use for time-stamping is to allow digital signatures to out-live
the validity period of a given public private key pair. If the
time-stamped signature shows that the document was signed during the
life-time of the signing key pair this provides additional assurance
that the signature is still valid despite the fact that the key is now
marked as expired, or was say later compromised and revoked.
Lots of other uses for time-stamping services also; I thought of a use
for them in the eternity service in preventing race conditions.
Adam
--
Now officially an EAR violation...
Have *you* exported RSA today? --> http://www.dcs.ex.ac.uk/~aba/rsa/
print pack"C*",split/\D+/,`echo "16iII*o\U@{$/=$z;[(pop,pop,unpack"H*",<>
)]}\EsMsKsN0[lN*1lK[d2%Sa2/d0<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<J]dsJxp"|dc`
Return to January 1998
Return to ““William H. Geiger III” <whgiii@invweb.net>”