1996-07-18 - Re: Opiated file systems

Header Data

From: The Deviant <deviant@pooh-corner.com>
To: “Mark O. Aldrich” <maldrich@grci.com>
Message Hash: 0de18f1b5907c1f06f154788b160f81a2c232cdb7902f9fbe8a969f10f787e42
Message ID: <Pine.LNX.3.94.960717194528.8968A-100000@switch.sp.org>
Reply To: <Pine.SCO.3.93.960716103725.10319B-100000@grctechs.va.grci.com>
UTC Datetime: 1996-07-18 06:01:42 UTC
Raw Date: Thu, 18 Jul 1996 14:01:42 +0800

Raw message

From: The Deviant <deviant@pooh-corner.com>
Date: Thu, 18 Jul 1996 14:01:42 +0800
To: "Mark O. Aldrich" <maldrich@grci.com>
Subject: Re: Opiated file systems
In-Reply-To: <Pine.SCO.3.93.960716103725.10319B-100000@grctechs.va.grci.com>
Message-ID: <Pine.LNX.3.94.960717194528.8968A-100000@switch.sp.org>
MIME-Version: 1.0
Content-Type: text/plain


-----BEGIN PGP SIGNED MESSAGE-----

On Tue, 16 Jul 1996, Mark O. Aldrich wrote:

> One problem, however, would be how to keep the "decoy" data, accessible
> with only the ambush key, "fresh" in that it must undergo a certain amount
> of
> turbulence to appear real.  The two file systems would essentially have to
> mirror each other, one with the juicy bits and one with the decoy bits.
> It would seem to be practically impossible to just build two file systems
> as one would 'disappear' when only the ambush key was used.  Wouldn't it
> be sort of obvious that something was wrong if half the disk vanished?
> 

While you do have a valid point about the turbulance needed, I think you
could still make some reasonable enough errors on the fakefs. One could
simple have several "curropt I-node tables", and that would satisfy almost
anybody (the NSA doesn't do domestic work ;)

 --Deviant


-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQEVAwUBMe1GlDAJap8fyDMVAQHUiwf/Tc1Oq8qxx6Q9T5r57RHaDIyDaANKkUas
1VvVR2eCMlfDQAvUAFbGELEErKRTQnb+JCF9QoCH/eLrAnFcKrk+4hbcONimongO
X3wTUn3PXhQSoF3XH7u9F13npo0cAWavmlJD+16uTFxtyzt211u/APuxHrT/9jWx
mgvQtgMwkqNJICSlIRHAL4pQJ6pe1cweR8t0UxpKy55WtQzsdyF2Yh3fYSDvyaaa
L3m9qaa2QBuuLpPr7Bd5iCGlsPiyv2lo73FF9biYiKOTbo1lIKX5Sy5ITJVBFmrM
tfw7ZCxoe281k0jyyO3524Vycd5VOBOfE0atgHfMClI/E7AH9v43FA==
=chgf
-----END PGP SIGNATURE-----






Thread