From: Milan Broz <gmazyland@gmail.com>
To: sven@whgl.uni-frankfurt.de, dm-crypt@saout.de
Subject: Re: [dm-crypt] cryptsetup upgrade to 1.6.x unlocking problem in initramfs
Date: Fri, 05 Sep 2014 17:29:26 +0200 [thread overview]
Message-ID: <5409D6D6.5050305@gmail.com> (raw)
In-Reply-To: <6899887c4cbe94228dea5619a57f64aa.squirrel@ssl.verfeiert.org>
On 09/05/2014 12:54 AM, Sven Eschenberg wrote:
> For me two major questions remain though:
> 1.) Why did an older version of cryptsetup work without these modules?
Hi,
HMAC is mandatory, so check your previous config... I guess just some magic
switched it to module... :)
> 2.) Why is HMAC needed? It is not obvious and if some other kernel module
> needs it, why is the dependecy missing?
It is not dependence for kernel module but requirement of PBKDF2 used in LUKS.
But as I said, it should report problems in more clear error messages...
> 4.) if HMAC dependecy is owed to cryptsetup specificly, is that documented
> already?
I do not think there is a list of required kernel modules. Perhaps it should
be added somewhere. But I am afraid exact list will depend on kernel versions and
other configuration (crypto mgr, fips, hw accel. support, ...)
In short, for kernel backend, AF_ALG must be supported in general.
Then for LUKS: generic hash support, specific hash used in LUKS and HMAC is required.
With 1.6.5 and later it will optionally utilize also skcipher interface (so you need
the block cipher and block mode used in LUKS header.
For TrueCrypt support you need the same, (hash, hmac, block cipher, block mode).
Perhaps man page or FAQ could be more descriptive here (... send a patch ;-)
Thanks,
Milan
next prev parent reply other threads:[~2014-09-05 15:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-01 19:32 [dm-crypt] cryptsetup upgrade to 1.6.x unlocking problem in initramfs Sven Eschenberg
2014-09-01 20:00 ` Milan Broz
2014-09-01 20:12 ` Sven Eschenberg
2014-09-01 20:41 ` Milan Broz
2014-09-01 21:35 ` Sven Eschenberg
2014-09-03 16:56 ` Milan Broz
2014-09-03 21:03 ` Sven Eschenberg
2014-09-04 7:24 ` Milan Broz
2014-09-04 22:54 ` Sven Eschenberg
2014-09-05 15:29 ` Milan Broz [this message]
2014-09-05 22:23 ` Arno Wagner
2014-09-05 22:39 ` Sven Eschenberg
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=5409D6D6.5050305@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-crypt@saout.de \
--cc=sven@whgl.uni-frankfurt.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.