1997-06-23 - Sources for stego images, was re: Laying PipeNet

Header Data

From: Steve Schear <azur@netcom.com>
To: Adam Back <aba@dcs.ex.ac.uk>
Message Hash: 3f93e6cf5ce03f415a67127fc75381451d42f6eea845e76e44c5de2f31eedd1b
Message ID: <v03102804afd38b324730@[]>
Reply To: <v03102802afd305494670@[]>
UTC Datetime: 1997-06-23 02:19:46 UTC
Raw Date: Mon, 23 Jun 1997 10:19:46 +0800

Raw message

From: Steve Schear <azur@netcom.com>
Date: Mon, 23 Jun 1997 10:19:46 +0800
To: Adam Back <aba@dcs.ex.ac.uk>
Subject: Sources for stego images, was re: Laying PipeNet
In-Reply-To: <v03102802afd305494670@[]>
Message-ID: <v03102804afd38b324730@[]>
MIME-Version: 1.0
Content-Type: text/plain

>That's the major problem with images, you need to generate your own.
>Unless you fancy writing an image enhancement system, and analyse the
>algorithms in existing systems to ensure that randomness is

There are plenty of Net-cams watching traffic or sunsets around the world.
Since these images tend to change a bit from frame to frame they could
cheaply and reliably provide the sorts of images which are ideal for stego.
I'm not sure if you can frame-grab from such a changing Web page with the
current browser features, but this should be a significant hurdle.


PGP mail preferred
Fingerprint: FE 90 1A 95 9D EA 8D 61  81 2E CC A9 A4 4A FB A9
Steve Schear              | tel: (702) 658-2654
CEO                       | fax: (702) 658-2673
First ECache Corporation  |
7075 West Gowan Road      |
Suite 2148                |
Las Vegas, NV 89129       | Internet: azur@netcom.com

        I know not what instruments others may use,
        but as for me, give me Ecache or give me debt.