Re: Compression and crypto
- From: daw@xxxxxxxxxxxxxxxxxxxxxxxx (David Wagner)
- Date: Thu, 25 May 2006 17:55:51 +0000 (UTC)
My complaint, again for clarity, is that while decompressions will lead
to strings with the correct alphabet [e.g. ASCII, binary, symbols of
your choosing] they won't follow a grammar [or even make sense].
For instance, you could map all random strings to decodable JPEGs but
will you also ensure the content of the JPEG makes sense and isn't just
white noise? Replace JPEG with a binary image [e.g. program] or text
document or HTML or PDF or ...I'll be able to tell the key was wrong by
checking if the decoded output makes any sense.
For what it's worth, I believe tomstdenis is absolutely correct here.
(He has made this point many times before, but somehow it doesn't seem
to have sunk in yet.)
.
- Follow-Ups:
- Re: Compression and crypto
- From: David A. Scott
- Re: Compression and crypto
- From: JR
- Re: Compression and crypto
- References:
- NSA and crypto
- From: David A. Scott
- Re: Compression and crypto
- From: tomstdenis
- Re: Compression and crypto
- From: David A. Scott
- Re: Compression and crypto
- From: tomstdenis
- NSA and crypto
- Prev by Date: Re: Resources required to retrieved wiped disk
- Next by Date: Re: Keylogger resistance
- Previous by thread: Re: Compression and crypto
- Next by thread: Re: Compression and crypto
- Index(es):
Relevant Pages
|