From: Moji <lordmoji@gmail.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] 1,5 TB partition: use cbc-essiv or xts-plain?
Date: Tue, 4 Aug 2009 00:46:26 +0300 [thread overview]
Message-ID: <20090804004626.4a811f96@gmail.com> (raw)
In-Reply-To: <20090803125342.CF87216440B5@mail.absint.com>
I am so sorry, I hit send before I had finished writing, I was delayed trying to find an article that I thought would help you with more explanation but I could not remember where I read it.
Finally I did locate it, it should provide some information on ESSIV for you: http://clemens.endorphin.org/LinuxHDEncSettings
Also, based on the information I have posted, and assuming that you will not be using raid to break up the device, I would recommend:
serpent-cbc-essiv:sha256
serpent because it is very strong cipher, even though it has not as much testing as AES, and cbc-essiv, because I have not seen any reports of inherent vulnerabilities on larger devices.
-MJ
On Mon, 3 Aug 2009 14:53:42 +0200 (CEST)
theiling@absint.com (Henrik Theiling) wrote:
> Hi!
>
> While trying to make a decision of how to encrypt a large disk, I
> found no good answer yet. What I am searching for is a site that
> gives me a simple overview of pros and cons of the different choices
> to be made when selecting LUKS algorithms. Yet, I found nothing like
> that.
>
> In this particular case: for a 1,5 TB partition, should I use
> cbc-essiv or xts-plain?
>
> It seems cbc-essiv is susceptible to watermarking (according to
> Wikipedia, which claims that no IV obfuscation algorithm protects
> against this except in the initial block. Unfortunately, I cannot
> verify this, so it sounds bad to me.
>
> And then, xts-plain is said to become weaker on large disks, and some
> crypto implementations warn about this weakness for disks as small as
> 500GB. So what's the alternative? (If I understand correctly, LUKS
> has no multi-key XTS option for large disks, right (in case that would
> overcome the problem)?)
>
> I don't seem to be able to make a decision on my own, so I'd like to
> ask for help. Which problem is worse? Or are there ways to overcome
> both problems? I could probably split the disk and re-assemble the
> xts-plain encrypted parts in a RAID, but that seems very complex.
> There don't need to be simple answers -- I am willing to evaluate my
> problem thoroughly, but so far I found no good comparison.
>
> Bye,
> Henrik
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
next prev parent reply other threads:[~2009-08-03 21:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-03 12:53 [dm-crypt] 1,5 TB partition: use cbc-essiv or xts-plain? Henrik Theiling
2009-08-03 14:34 ` Heinz Diehl
2009-08-03 16:16 ` Henrik Theiling
2009-08-03 17:34 ` Heinz Diehl
2009-08-03 17:37 ` Heinz Diehl
2013-01-03 9:50 ` Peter Pfundstein
2009-08-03 14:43 ` [dm-crypt] E3E-2A1 - 1, 5 " Heinz Diehl
2009-08-03 20:48 ` [dm-crypt] 1,5 " Moji
2009-08-04 7:42 ` Milan Broz
2009-08-04 13:01 ` Henrik Theiling
2009-08-03 21:46 ` Moji [this message]
2009-08-04 13:27 ` Henrik Theiling
2009-08-04 13:55 ` Moji
2009-08-06 11:02 ` Salatiel Filho
2009-08-06 14:32 ` Henrik Theiling
2009-08-06 15:24 ` Heinz Diehl
2009-08-06 16:00 ` Salatiel Filho
2009-08-06 16:02 ` Salatiel Filho
2009-08-07 12:16 ` Salatiel Filho
2009-08-07 12:20 ` Salatiel Filho
2009-08-07 16:00 ` Salatiel Filho
2009-08-08 8:27 ` Heinz Diehl
2009-08-08 10:03 ` Salatiel Filho
2009-08-06 15:43 ` Sam
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=20090804004626.4a811f96@gmail.com \
--to=lordmoji@gmail.com \
--cc=dm-crypt@saout.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox