From: Milan Broz <mbroz@redhat.com>
To: Maciej Pilichowski <bluedzins@wp.pl>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] How to activate hash module?
Date: Sun, 13 Mar 2011 19:29:38 +0100 [thread overview]
Message-ID: <4D7D0D12.2020303@redhat.com> (raw)
In-Reply-To: <201103131623.19883.bluedzins@wp.pl>
>> What is the hash in question?
>
> Ok, it is ripemd 320.
>> The best is paste error messages (add --debug) so it is clear what
>> is the exact problem.
>
> Code 22: Requested LUKS hash ripemd320 is not supported.
...and you will be surprised with answer :)
It is for LUKS hash, so it is userspace, no kernel related thing.
AFAIK gcrypt never supported rmd320 (only rmd160 - just checked git tree).
But because LUKS ignored -h switch in older versions (with hardcoded sha1),
it probably quetly worked until you upgraded to newer cryptsetup,
which now honors -h switch now.
(Hash switch was useful only for plain mapping for passphrase hashing.)
Easy to verify: run crypsetup luksDump and check "Hash spec".
I guess it is "sha1", if so, simply remove rmd320 hash option and
it will work again.
Milan
next prev parent reply other threads:[~2011-03-13 18:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-13 9:45 [dm-crypt] How to activate hash module? Maciej Pilichowski
2011-03-13 10:53 ` Heinz Diehl
2011-03-13 13:47 ` Milan Broz
2011-03-13 15:23 ` Maciej Pilichowski
2011-03-13 18:29 ` Milan Broz [this message]
2011-03-13 18:58 ` Maciej Pilichowski
2011-03-13 20:22 ` Milan Broz
2011-03-14 15:54 ` Maciej Pilichowski
2011-03-14 16:32 ` Arno Wagner
2011-03-14 20:01 ` Maciej Pilichowski
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=4D7D0D12.2020303@redhat.com \
--to=mbroz@redhat.com \
--cc=bluedzins@wp.pl \
--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.