From: Eric Bauman <baumane@livejournal.dk>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] LUKS --hash vs. --cipher whatever:hash
Date: Sun, 20 Feb 2011 05:39:18 +1100 [thread overview]
Message-ID: <ijp2om$plj$1@dough.gmane.org> (raw)
In-Reply-To: <4D5ECBC2.1060302@redhat.com>
Thanks for the replies.
On 19/02/2011, Milan Broz wrote:
> --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.)
Is there any benefit to hash size / algorithm strength? It seems like
afsplitter will ensure the split key is the required length regardless
of the hash output.
> 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).
Does using sha256 over some other hash outputting only 128 bits offer
any practical benefit, other than decreasing the likelyhood of two IVs
being the same?
> It is part of the specification - for more info see project pages
> http://code.google.com/p/cryptsetup/ - specification bookmark.)
Thanks for the link, interesting reading.
Thanks,
Eric
prev parent reply other threads:[~2011-02-19 18:39 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
2011-02-19 18:39 ` Eric Bauman [this message]
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='ijp2om$plj$1@dough.gmane.org' \
--to=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