From: Sitaram Chamarty <sitaramc@gmail.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] security: improve defaults
Date: Sat, 03 Jan 2015 13:49:00 +0530 [thread overview]
Message-ID: <54A7A5F4.5000908@gmail.com> (raw)
In-Reply-To: <20150103060055.GB31120@tansi.org>
On 01/03/2015 11:30 AM, Arno Wagner wrote:
> On Sat, Jan 03, 2015 at 00:18:21 CET, Christian Stadelmann wrote:
>> cipher: aes-cbc-essiv (default in plain mode)
>> There are known attacs against aes-cbc-essiv which lead to using aes-xts
>> as default cipher in LUKS mode. Is there any reason why it should not be
>> used in plain mode?
>
> Simple: Backwards compatibility. As plain mode does not
> have a header, this would break old uses. Anybody that wants
> it can already use XTS.
seconded; I rely on this -- please don't change this :-)
Christian: anyone who is using dm-crypt in plain mode *already* knows
what he is doing. If they don't, they should not be using plain mode.
There is no need for you or me to worry about them, in my opinion.
next prev parent reply other threads:[~2015-01-03 8:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-02 23:18 [dm-crypt] security: improve defaults Christian Stadelmann
2015-01-03 6:00 ` Arno Wagner
2015-01-03 8:19 ` Sitaram Chamarty [this message]
2015-01-03 9:08 ` Milan Broz
2015-01-04 1:59 ` Sven Eschenberg
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=54A7A5F4.5000908@gmail.com \
--to=sitaramc@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