From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] list of supported encryption options for LUKS
Date: Tue, 9 Sep 2014 00:33:09 +0200 [thread overview]
Message-ID: <20140908223309.GA19869@tansi.org> (raw)
In-Reply-To: <CAFnMBaT62qeLYz4dwdHd1L7UcCxseU4hFO8MamkxF-A10bF6BQ@mail.gmail.com>
On Mon, Sep 08, 2014 at 21:42:06 CEST, .. ink .. wrote:
> On Sun, Sep 7, 2014 at 12:59 PM, Milan Broz <gmazyland@gmail.com> wrote:
>
>
>
> > But I still think that there should be only few strong predefined
> > combinations.
> >
> >
> The list of option i am going to support for LUKS volumes is listed below
> as taken from cryptsetup benchmark list.
>
> First condition is for plain volumes,second condition for luks and the last
> one is for truecrypt.
>
> https://github.com/mhogomchungu/zuluCrypt/blob/c99841c21a6edeea955106134fd54d5935f8e237/zuluCrypt-gui/createvolume.cpp#L238
I would add a warning about gcrypt (see FAQ 8.3) for all
variants with whirlpool. Some people may still use this with
the broken gcrypt implementation.
Apart from that, the list looks fine.
Side-question:
Are the multi-cipher variants like "twofish:aes.xts-plain64.256.ripemd160"
something you do yourself? How do you do them? Additional
LUKS layers with the same passphrase set-up?
Arno
--
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
----
A good decision is based on knowledge and not on numbers. -- Plato
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
next prev parent reply other threads:[~2014-09-08 22:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-07 16:15 [dm-crypt] list of supported encryption options for LUKS .. ink ..
2014-09-07 16:59 ` Milan Broz
2014-09-07 17:30 ` .. ink ..
2014-09-07 22:11 ` Arno Wagner
2014-09-07 22:05 ` Arno Wagner
2014-09-08 19:42 ` .. ink ..
2014-09-08 22:33 ` Arno Wagner [this message]
2014-09-08 22:38 ` Arno Wagner
2014-09-09 1:19 ` .. ink ..
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=20140908223309.GA19869@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.