1998-09-22 - Re: Stego-empty hard drives… (fwd)

Header Data

From: Jim Choate <ravage@einstein.ssz.com>
To: cypherpunks@einstein.ssz.com (Cypherpunks Distributed Remailer)
Message Hash: c146eada5295378ed6084102b37c7c879d4c021de4a6ea1b53b4edb9a9879de9
Message ID: <199809221743.MAA05104@einstein.ssz.com>
Reply To: N/A
UTC Datetime: 1998-09-22 04:18:36 UTC
Raw Date: Tue, 22 Sep 1998 12:18:36 +0800

Raw message

From: Jim Choate <ravage@einstein.ssz.com>
Date: Tue, 22 Sep 1998 12:18:36 +0800
To: cypherpunks@einstein.ssz.com (Cypherpunks Distributed Remailer)
Subject: Re: Stego-empty hard drives... (fwd)
Message-ID: <199809221743.MAA05104@einstein.ssz.com>
MIME-Version: 1.0
Content-Type: text



Forwarded message:

> Date: Tue, 22 Sep 1998 11:07:34 -0500
> From: Petro <petro@playboy.com>
> Subject: Re: Stego-empty hard drives... (fwd)

> 	I don't know how hard this would be, but how about running a
> seperate memory check, and while those numbers are flashing on the screen,
> do the wait for imput?

So hide the keyscan in the memory counter code. Would work externaly, would
probably not show up on TEMPEST. Since both the keyscan and the memory scan
are repetitive TEMPEST might have a problem telling them apart. Provided you
could get the keyscan in the same footprint as the mem check the BIOS
would not show up as anomolous in size. As long as they're not running
around doing checksums you'd be ok (I suspect).


    ____________________________________________________________________

                            The seeker is a finder.

                                     Ancient Persian Proverb

       The Armadillo Group       ,::////;::-.          James Choate
       Austin, Tx               /:'///// ``::>/|/      ravage@ssz.com
       www.ssz.com            .',  ||||    `/( e\      512-451-7087
                           -====~~mm-'`-```-mm --'-
    --------------------------------------------------------------------





Thread