From: anonymous-remailer@shell.portal.com
To: cypherpunks@toad.com
Message Hash: 97fdc0aa31863d9959814fb4ea3b6db45b2426feb595da7329dad3ae70b9d041
Message ID: <199606020213.TAA00981@jobe.shell.portal.com>
Reply To: N/A
UTC Datetime: 1996-06-02 05:15:58 UTC
Raw Date: Sun, 2 Jun 1996 13:15:58 +0800
From: anonymous-remailer@shell.portal.com
Date: Sun, 2 Jun 1996 13:15:58 +0800
To: cypherpunks@toad.com
Subject: Re: Compressed data vulnerable to known-plaintext?
Message-ID: <199606020213.TAA00981@jobe.shell.portal.com>
MIME-Version: 1.0
Content-Type: text/plain
Someone who claimed to be Mark M. said on Sat, 1 Jun 1996:
(I said:)
> > Why not simply use two session keys, and encrypt the headers with one
> > while encrypting the actual data with the other? That seems to solve both
> > problems, except that more CPU cycles are required.
>
> An easier solution would be to just strip of the headers. If the header is
> always the same, then it is redundant. If it varies, then it cannot be used
> as known-plaintext.
But then you still have the problem of identifying the contents. If there
were no headers, one could not tell if the message was compressed using
ZIP, LHA, StuffIt, tar*, compress, gzip, Alice's Magical Supercompressor,
or even if it was left alone. One could also not tell if the decryption
happened successfully.
( * Yes, I know tar is not compression. )
Return to June 1996
Return to ““Mark M.” <markm@voicenet.com>”