1994-02-08 - Re: Clipper Side-step

Header Data

From: qwerty-remailer@netcom.com
To: cypherpunks@toad.com
Message Hash: cfaffa41183e8854c2f64badad12b1e5a7dec6b740e0493fcf1da1e078a40ca1
Message ID: <199402081842.KAA22638@mail.netcom.com>
Reply To: N/A
UTC Datetime: 1994-02-08 18:42:00 UTC
Raw Date: Tue, 8 Feb 94 10:42:00 PST

Raw message

From: qwerty-remailer@netcom.com
Date: Tue, 8 Feb 94 10:42:00 PST
To: cypherpunks@toad.com
Subject: Re: Clipper Side-step
Message-ID: <199402081842.KAA22638@mail.netcom.com>
MIME-Version: 1.0
Content-Type: text/plain


Beep say,
"How about this as a way to stump Clipper?

Generate a dialog between you and a friend of no relevant consequence.
Load this sound byte into your system as a AIFC file (sound bite, or byte)
Encrypt data/message/information/recipe/whatever into the low-bits of
the sound bite."

See my post "X's Last R". The problem is that PGP tattle tales on itself, it
having no raw encrypted message output format (~indistinguishable from random
data), and thus reverse steganography is trivial and can be automated. It could
be less trivial if you use a steganography (hiding a message in another
message) along with a secret scrambling routine for PGP messages, but then
you are in the silly situation of "encrypting" an already encrypted PGP
message!

 -=Xenon=-






Thread