1996-03-02 - Re: Chaff in the Channel (Stealth PGP work)

Header Data

From: Mike Fletcher <fletch@ain.bls.com>
To: cypherpunks@toad.com
Message Hash: cf51f5015c52d785fc93764019a98e381f70bf87360768e232f0e13cef6852e5
Message ID: <9603021720.AA04821@outland>
Reply To: <E87A6630BA@st.vse.cz>
UTC Datetime: 1996-03-02 17:58:57 UTC
Raw Date: Sun, 3 Mar 1996 01:58:57 +0800

Raw message

From: Mike Fletcher <fletch@ain.bls.com>
Date: Sun, 3 Mar 1996 01:58:57 +0800
To: cypherpunks@toad.com
Subject: Re: Chaff in the Channel (Stealth PGP work)
In-Reply-To: <E87A6630BA@st.vse.cz>
Message-ID: <9603021720.AA04821@outland>
MIME-Version: 1.0
Content-Type: text/plain


>     the problem with many current stego programs (jsteg/stools) is 
> that given a data stream, they will tell you if there is data steg'ed 
> (by the same program, of course) it in. jsteg goes out of it's way to 
> hide it's content-length header, but jsteg can still detect jsteg 
> headers...

	Just a stab, but maybe this might work:  Get two picures of
with both at minimum sufficient size to carry the message.  Use the
lsb's (or any bit for that matter) of the second image to XOR with the
message before stego'ing (L'eggo my S'tego :) into the first.  Of course
you'ld have to arrange which bit in the pad image will be used, how to
associate the images, etc. before hand.

---
Fletch                                                     __`'/|
fletch@ain.bls.com  "Lisa, in this house we obey the       \ o.O'    ______
404 713-0414(w)      Laws of Thermodynamics!" H. Simpson   =(___)= -| Ack. |
404 315-7264(h) PGP Print: 8D8736A8FC59B2E6 8E675B341E378E43  U      ------





Thread