1993-05-26 - Re: Steganography

Header Data

From: peter honeyman <honey@citi.umich.edu>
To: wcs@anchor.ho.att.com
Message Hash: 7cbd8a1e910262f6b045d12043397c1a2941f47d941b092e353b3a8bfaf688d1
Message ID: <9305260358.AA07063@toad.com>
Reply To: <9305260134.AA21012@anchor.ho.att.com>
UTC Datetime: 1993-05-26 03:58:09 UTC
Raw Date: Tue, 25 May 93 20:58:09 PDT

Raw message

From: peter honeyman <honey@citi.umich.edu>
Date: Tue, 25 May 93 20:58:09 PDT
To: wcs@anchor.ho.att.com
Subject: Re: Steganography
In-Reply-To: <9305260134.AA21012@anchor.ho.att.com>
Message-ID: <9305260358.AA07063@toad.com>
MIME-Version: 1.0
Content-Type: text/plain


>                                  A more serious concern is compressibility -
> a real image file is probably more compressible than a file with the
> low-order bit replaced by a crypto-bit, since the real data has moderate
> correlation and the crypto-bits are random.  I doubt the Feds will immediately
> start looking to see if you're shipping GIF files that have significantly
> worse compression than average, but they'd probably find something if they did it.

how many bits are we talking about here?  suppose it's two in sixteen.
7/8 of the compressible bits remain.  so if the normal compressibility
is 2:1, taking two out of sixteen bits would leave 1.75:1 compression.
is that a "notable" difference?

i haven't been paying close enough attention -- is two out of sixteen
a realistic amount?  it seems high to me.  if it's one out of sixteen,
the effect is only a 6.25% reduction in compression.  is that notable?

	peter





Thread