1995-09-05 - Re: Emergency File Wipe Algorithim

Header Data

From: monty.harder@famend.com (MONTY HARDER)
To: CYPHERPUNKS@toad.com
Message Hash: b6bc42546809250db6cf7e5a03d9d5aaf8c4c067df5a009ec6270135aee1d9f3
Message ID: <8B074DD.00030003EA.uuout@famend.com>
Reply To: N/A
UTC Datetime: 1995-09-05 03:44:01 UTC
Raw Date: Mon, 4 Sep 95 20:44:01 PDT

Raw message

From: monty.harder@famend.com (MONTY HARDER)
Date: Mon, 4 Sep 95 20:44:01 PDT
To: CYPHERPUNKS@toad.com
Subject: Re: Emergency File Wipe Algorithim
Message-ID: <8B074DD.00030003EA.uuout@famend.com>
MIME-Version: 1.0
Content-Type: text/plain


CW> and relaxation are in the same order of magnitude.  Thus, a few microseconds of
CW> storing the opposite data to the currently stored value will have little effect
CW> on the oxide.  Ideally, the oxide should be exposed to as much stress at the

  Here is a simple way to handle the problem, using our old discredited
friend, XOR. Set up your software to periodically XOR the key with FFFF.
This way, each bit will be a 0 half the time, and a 1 the other half.
You have a flag that tells whether the key is in normal or inverted
form, so that you can quickly perform any necessary computations on it,
but there should not be any long-term memory effect.


 * Free will made me do it!
---
 * Monster@FAmend.Com *    





Thread