From: Stefan Xenon <stefanxe@gmx.net>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] different default key sizes for CREATE and LUKSFORMAT
Date: Wed, 18 Nov 2009 11:01:18 +0100 [thread overview]
Message-ID: <4B03C5EE.7010702@gmx.net> (raw)
In-Reply-To: <20091118054555.GB28949@tansi.org>
If the reason is historically only, it might be a kind of security issue
(low priority) because this behaviour could result in wrong expectations
of users on the system regarding the default key size. A user who learns
that the default key size (using "create") is 256 bit but uses
"luksFormat" (which uses 128 bit) instead, may be misleaded. Therefore
it may be better to harmonize both default values.
Stefan
Arno Wagner schrieb:
> "create" is plain dm-crypt, luskFormat is creation of
> a LUKS header. I suspect the reason is historical, as
> these are two different encryption systems.
>
> Arno
>
>
>
> On Tue, Nov 17, 2009 at 11:45:40PM +0100, Stefan Xenon wrote:
>> Hi!
>> In the man page for cryptsetup is written regarding the option --key-size :
>>
>> "Can be used for create or luksFormat, all
>> other LUKS actions will ignore this flag, as the key-size is
>> specified by the partition header. Default is 128 for luksFormat
>> and 256 for create."
>>
>> I am wondering what is the reason for two different default key sizes?
>>
>> Thanks
>> Stefan
>>
>> _______________________________________________
>> dm-crypt mailing list
>> dm-crypt@saout.de
>> http://www.saout.de/mailman/listinfo/dm-crypt
>>
>
next prev parent reply other threads:[~2009-11-18 10:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 22:45 [dm-crypt] different default key sizes for CREATE and LUKSFORMAT Stefan Xenon
2009-11-18 5:45 ` Arno Wagner
2009-11-18 10:01 ` Stefan Xenon [this message]
2009-11-18 10:25 ` Arno Wagner
2009-11-18 11:20 ` Milan Broz
2009-11-18 13:26 ` Milan Broz
2009-11-18 15:17 ` Heinz Diehl
2009-11-19 7:41 ` Arno Wagner
2009-11-19 9:21 ` Heinz Diehl
2009-11-19 12:24 ` Arno Wagner
2009-11-19 12:28 ` Arno Wagner
2009-11-19 13:00 ` Heinz Diehl
2009-11-20 12:14 ` Milan Broz
2009-11-20 15:43 ` Heinz Diehl
2009-11-21 10:47 ` Arno Wagner
2009-11-21 12:40 ` Stefan Xenon
2009-11-21 17:26 ` Arno Wagner
2009-11-19 20:00 ` Stefan Xenon
2009-11-20 12:22 ` Milan Broz
2009-11-23 13:45 ` Roscoe
2009-11-23 14:29 ` Milan Broz
2009-11-23 15:46 ` Arno Wagner
2009-11-23 16:05 ` Heinz Diehl
2009-11-19 7:28 ` Arno Wagner
2009-11-20 12:43 ` Jonas Meurer
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=4B03C5EE.7010702@gmx.net \
--to=stefanxe@gmx.net \
--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.