From: Gregory Maxwell <gmaxwell@gmail.com>
To: "Valdis.Kletnieks@vt.edu" <Valdis.Kletnieks@vt.edu>
Cc: David Masover <ninja@slaphack.com>,
Edward Shishkin <edward@namesys.com>,
Fred Schaettgen <namesys.Sch@ttgen.net>,
reiserfs-list@namesys.com
Subject: Re: Will I need to re-format my partition for using the compression plugin?
Date: Thu, 22 Sep 2005 18:13:23 -0400 [thread overview]
Message-ID: <e692861c050922151366608976@mail.gmail.com> (raw)
In-Reply-To: <200509222049.j8MKn1CH012169@turing-police.cc.vt.edu>
On 9/22/05, Valdis.Kletnieks@vt.edu <Valdis.Kletnieks@vt.edu> wrote:
> 1) RSA is useless for this - you really need a symmetric block cipher of some
> sort. Almost all block ciphers are best used with maximum-entropy input - if
> the attacker can lop out a large part of the keyspace, a brute force attack
> becomes a lot easier. This is somewhat related to the concept of "Hamming
> Distance". If the attacker tries a brute force attack, and the first 8 bytes of
> the output look like valid HTML, or English text, or anything else
> recognizable, he's almost certainly found found the correct key. On the other
> hand, well-compressed data has very high entropy - as a result, it becomes
> harder to tell if a correct key has been found. If it's English text, but
> 3 of the first 8 bytes have the high bit set, it's probably not a correct key.
> If it's compressed, 3 flipped bits in the first 8 bytes will probably still
> represent a valid compressed stream - just of something else wildly different.
It would normally seem silly to use RSA for disk encryption... but
there might be applications, although you'd still never use RSA
directly on user controlled data. For example, RSA could be used on a
multi user server to append mail to a mail file so that once written
the data is only accessible once the user logs on. The reiser4 crypto
system will use the kernel keyring api, so it would be quite
reasonable to tie encryption to user accounts. 'write only' files and
'read only' files would be a simple logical extension, and would
require asymetric cryptography.
Although for most compression algorithms not all inputs are valid
outputs, so this may not work for you... It would be ideal (for disk
encryption) if it were not possible to tell if you have the right key
without decrypting an entire sector. This requires careful selection
in compression and chaining mode. Alternatively, it may be possible
to develop a good large block cipher which while being much slower
than a single block of a small-block cipher, is faster for a disk
block. For example, mercy is about 4x faster than AES on my system
but is still 16x slower for the smallest unit of decryption than AES.
Unfortunately mercy has security problems.
> 2) Even though most modern block ciphers are designed to be fast, it's still
> faster to apply a reasonably quick compression scheme to whomp 16K of data
> down to 5-6K and encrypt/decrypt 5-6k than it is to encrypt/decrypt 16K.
Depends on the compression mode and the cipher. A good AES
implementation is around the same speed as an aggressive gzip. In
general this is correct.
next prev parent reply other threads:[~2005-09-22 22:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-20 13:31 Will I need to re-format my partition for using the compression plugin? Clemens Eisserer
2005-09-20 13:58 ` Edward Shishkin
2005-09-20 15:49 ` Vladimir V. Saveliev
2005-09-20 16:12 ` Edward Shishkin
2005-09-20 19:19 ` Clemens Eisserer
2005-09-20 19:38 ` Tomasz Chmielewski
2005-09-20 19:43 ` Edward Shishkin
2005-09-22 15:24 ` Grzegorz Jaśkiewicz
2005-09-22 16:41 ` Edward Shishkin
2005-09-22 17:51 ` Fred Schaettgen
2005-09-22 20:03 ` Edward Shishkin
2005-09-22 20:11 ` David Masover
2005-09-22 20:49 ` Valdis.Kletnieks
2005-09-22 20:54 ` michael chang
2005-09-22 21:05 ` Valdis.Kletnieks
2005-09-23 9:00 ` Edward Shishkin
2005-09-22 22:13 ` Gregory Maxwell [this message]
2005-09-23 6:08 ` Valdis.Kletnieks
2005-09-22 20:38 ` Valdis.Kletnieks
2005-09-22 20:54 ` Gregory Maxwell
2005-09-22 21:33 ` PFC
2005-09-22 21:38 ` Fred Schaettgen
2005-09-23 11:12 ` Edward Shishkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e692861c050922151366608976@mail.gmail.com \
--to=gmaxwell@gmail.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=edward@namesys.com \
--cc=namesys.Sch@ttgen.net \
--cc=ninja@slaphack.com \
--cc=reiserfs-list@namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.