From: keelings@wu1.wl.aecl.ca (S. Keeling)
To: cypherpunks@toad.com
Message Hash: aa30b60910b0c9c5502b446d3f30dd2783c2f4c6893da5c20a49546be06326af
Message ID: <9509191427.AA23942@wu1.wl.aecl.ca>
Reply To: N/A
UTC Datetime: 1995-09-19 14:28:57 UTC
Raw Date: Tue, 19 Sep 95 07:28:57 PDT
From: keelings@wu1.wl.aecl.ca (S. Keeling)
Date: Tue, 19 Sep 95 07:28:57 PDT
To: cypherpunks@toad.com
Subject: Time release crypto
Message-ID: <9509191427.AA23942@wu1.wl.aecl.ca>
MIME-Version: 1.0
Content-Type: text/plain
Incoming from Stephen D. Williams:
>
> What minimal requirements would be needed to support encrypted packets/files
> that a holder could only decrypt after a certain date/time?
> (Time Escrow?)
How do you expect the system to reliably tell accurate time?
What's to stop anyone from just resetting the clock to get at what
they want?
As always, physical access to the system breaks all security.
--
"Remember, obsolescence (Win95) isn't an accident; it's an art form!"
keelings@wu1.wl.aecl.ca s. keeling, aecl - whiteshell labs
Return to September 1995
Return to “keelings@wu1.wl.aecl.ca (S. Keeling)”
1995-09-19 (Tue, 19 Sep 95 07:28:57 PDT) - Time release crypto - keelings@wu1.wl.aecl.ca (S. Keeling)