Clipper Side-step

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.
Play message over Clipper-infested line to waiting system.

[ Yes, you could just encrypt a message and send it, but in the above
situation, fleas-on-the-line would not even know data was being transfered
as they listened to Aunt Agnes talk about broccoli casserole.             ]

Just bouncing ideas...

> How about this as a way to stump Clipper?
[...]
> Encrypt data/message/information/recipe/whatever into the low-bits of
> the sound bite.

The low bits would probably be destroyed just by transmission over
your average voice line.  Worse, Clipperfones will compress the
input speech before encryption.  The only respectable audio
compression algorithms are lossy, and they will assuredly stomp on
your low bits.  Nor can you expect other modulations to survive
(e.g. the "data --> 212A --> Clipper --> 212A --> data" approach).

Given knowledge of the audio model used, you could take your data
stream and put it through the decompressor end.  The resultant
audio would be invariant under the lossy compression/decompression.

/--  sender  --\ /----          Clipper phone          ----\  /--  rcvr  --\
data->decompress->compress->encrypt,send,decrypt->decompress->compress->data
      \--   (cancel)   --/			  \--   (cancel)   --/

This would probably end up being manufacturer-specific and a real
pain.  Subverting a Capstone-based datacomm device would be easier.

   Eli   ebrandt@jarthur.claremont.edu