From: Milan Broz <mbroz@redhat.com>
To: Eric Bauman <baumane@livejournal.dk>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] LUKS --hash vs. --cipher whatever:hash
Date: Fri, 18 Feb 2011 20:42:58 +0100 [thread overview]
Message-ID: <4D5ECBC2.1060302@redhat.com> (raw)
In-Reply-To: <ijmc1r$lgb$1@dough.gmane.org>
On 02/18/2011 06:59 PM, Eric Bauman wrote:
> I'm interested in the difference between, --hash sha256 and --cipher
> whatever:sha256.
Hi,
For LUKS mode (luksFormat / luksOpen):
--hash is for LUKS header hash (by default is it sha1), IOW the hash
used for anti-forensic splitter and volume key obfuscation (passphrase
is used to unlock LUKS keyslots whe is volume key stored. Volume
key is always generated from random generator during format.)
sha256 in cipher specification is useful only for ESSIV initialization vector.
e.g. aes-cbc-essiv:sha256 - means cipher AES in CBC mode and with ESSIV
initialization vector which uses sha256 (IV is derived from key using
sha256 hash).
(For othes modes, like XTS, you do not need to use ESSIV because
the problem of predictable IV is solved by mode itself - so you can have
e.g. aes-xts-plain64. For LUKS header you must use some hash always.
It is part of the specification - for more info see project pages
http://code.google.com/p/cryptsetup/ - specification bookmark.)
For plain mode (cryptsetup create command):
--hash means which hash alg. will be used to generate key.
(passphrase is hashed and its output is directly used as key).
cipher specification is the same as in LUKS mode.
Milan
next prev parent reply other threads:[~2011-02-18 19:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 17:59 [dm-crypt] LUKS --hash vs. --cipher whatever:hash Eric Bauman
2011-02-18 19:42 ` Milan Broz [this message]
2011-02-19 18:39 ` Eric Bauman
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=4D5ECBC2.1060302@redhat.com \
--to=mbroz@redhat.com \
--cc=baumane@livejournal.dk \
--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