1994-06-11 - Re: Delayed self-encrypting messages
Header Data
From: Jim choate <ravage@bga.com>
To: kentborg@world.std.com (Kent Borg)
Message Hash: 1b78a33c6f40981f0d60dbf3f90c15756e26a715bb6e3b06f9c9957957851039
Message ID: <199406112245.RAA04963@zoom.bga.com>
Reply To: <199406110402.AA13528@world.std.com>
UTC Datetime: 1994-06-11 22:45:38 UTC
Raw Date: Sat, 11 Jun 94 15:45:38 PDT
Raw message
From: Jim choate <ravage@bga.com>
Date: Sat, 11 Jun 94 15:45:38 PDT
To: kentborg@world.std.com (Kent Borg)
Subject: Re: Delayed self-encrypting messages
In-Reply-To: <199406110402.AA13528@world.std.com>
Message-ID: <199406112245.RAA04963@zoom.bga.com>
MIME-Version: 1.0
Content-Type: text
I would look at monitoring some large scale system that is not easily
modelled so it can't be predicted faster than it actualy occurs.
This way when the appropriate condition occurs its digitized state
could be used as a key.
Thread
Return to June 1994
- Return to “Jim choate <ravage@bga.com>”
Return to “kentborg@world.std.com (Kent Borg)”
- 1994-06-11 (Fri, 10 Jun 94 21:03:26 PDT) - Re: Delayed self-encrypting messages - kentborg@world.std.com (Kent Borg)
- 1994-06-11 (Sat, 11 Jun 94 15:45:38 PDT) - Re: Delayed self-encrypting messages - Jim choate <ravage@bga.com>