From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Switch to XTS mode for LUKS in cryptsetup in 1.6.0 (Was Re: [ANNOUNCE] cryptsetup 1.6.0-rc1)
Date: Fri, 4 Jan 2013 17:17:03 +0100 [thread overview]
Message-ID: <20130104161703.GA22218@tansi.org> (raw)
In-Reply-To: <50E6C1EC.1000307@gmail.com>
On Fri, Jan 04, 2013 at 12:50:04PM +0100, Milan Broz wrote:
> On 12/29/2012 10:40 PM, Milan Broz wrote:
> > The testing release candidate cryptsetup 1.6.0-rc1 is available at
> >
> > http://code.google.com/p/cryptsetup/
> >
> > Feedback and bug reports are welcomed.
> >
> > Cryptsetup 1.6.0 Release Notes (RC1)
>
>
> I am going to do one more important change to final 1.6.0:
> change LUKS _default_ cipher to aes-xts-plain64 with 512bits key.
I think this is a very good idea.
Arno
> Most of recent disk encryption systems switched already to XTS mode,
> also it is preferred by standards (and we are using it for very long
> time in Fedora/RHEL during installations.)
>
> Distro maintainers can always overwrite this during compilation time,
> and user can use -c aes-cbc-essiv:sha256 -s 256 to old mode always.
>
> (Plain mode have to stay with CBC, change would cause compatibility problems.)
>
> Any serious objections to not do that now?
>
> Milan
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
One of the painful things about our time is that those who feel certainty
are stupid, and those with any imagination and understanding are filled
with doubt and indecision. -- Bertrand Russell
next prev parent reply other threads:[~2013-01-04 16:17 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-29 21:40 [dm-crypt] [ANNOUNCE] cryptsetup 1.6.0-rc1 Milan Broz
2012-12-29 22:24 ` Matthias Schniedermeyer
2012-12-29 22:42 ` Milan Broz
2012-12-29 23:21 ` Matthias Schniedermeyer
2012-12-29 23:15 ` Matthias Schniedermeyer
2012-12-29 23:31 ` Milan Broz
2013-01-02 12:50 ` Matthias Schniedermeyer
2013-01-02 20:55 ` Milan Broz
2012-12-30 8:38 ` Arno Wagner
2012-12-30 8:56 ` Sven Eschenberg
2012-12-30 10:20 ` Arno Wagner
2012-12-30 11:40 ` Milan Broz
2013-01-06 12:16 ` Yves-Alexis Perez
2013-01-06 16:24 ` Milan Broz
2013-01-07 6:23 ` Yves-Alexis Perez
2013-01-07 8:53 ` Milan Broz
2013-01-07 11:21 ` Sven Eschenberg
2013-01-07 18:12 ` Milan Broz
2013-01-07 19:20 ` Sven Eschenberg
2013-01-21 21:01 ` Yves-Alexis Perez
2012-12-30 11:47 ` Milan Broz
2013-01-05 19:47 ` Jonas Meurer
2012-12-30 9:03 ` Milan Broz
2013-01-04 11:50 ` [dm-crypt] Switch to XTS mode for LUKS in cryptsetup in 1.6.0 (Was Re: [ANNOUNCE] cryptsetup 1.6.0-rc1) Milan Broz
2013-01-04 11:53 ` Ralf Ramsauer
2013-01-04 12:18 ` Milan Broz
2013-01-04 16:26 ` Arno Wagner
2013-01-04 20:20 ` Heinz Diehl
2013-01-04 20:56 ` Milan Broz
2013-01-04 22:05 ` Arno Wagner
2013-01-04 22:39 ` Milan Broz
2013-01-05 17:20 ` Arno Wagner
2013-01-05 18:25 ` Milan Broz
2013-01-05 19:47 ` Arno Wagner
2013-01-04 13:39 ` Christoph Anton Mitterer
2013-01-04 16:17 ` Arno Wagner [this message]
2013-01-04 17:36 ` Zdenek Kaspar
2013-01-04 18:55 ` Romain Francoise
2013-01-04 19:14 ` Milan Broz
2013-01-04 21:56 ` Arno Wagner
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=20130104161703.GA22218@tansi.org \
--to=arno@wagner.name \
--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 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.