All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <mbroz@redhat.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] How to activate hash module?
Date: Sun, 13 Mar 2011 14:47:33 +0100	[thread overview]
Message-ID: <4D7CCAF5.3050903@redhat.com> (raw)
In-Reply-To: <20110313105332.GA6745@fancy-poultry.org>

On 03/13/2011 11:53 AM, Heinz Diehl wrote:
> On 13.03.2011, Maciej Pilichowski wrote: 
> 
>> Just of curiosity I tried to load the module explicitly (modprobe) 
>> in 11.4 and then execute cryptsetup again, but it still stated the 
>> hash is not supported.
> 
> Not quite shure on that one, but as far as I know, newer cryptsetup is
> libgcrypt based, so you'll have to check if your libgcrypt
> implementation has compiled-in support for this particular hash
> algorithm you're trying to use.

There are two uses for hash - one is for userspace (LUKS and passphrase
hashing in plain mode) and the second is used in ESSIV in kernel.

The best is paste error messages (add --debug) so it is clear what is
the exact problem.

If it is about kernel part, dmcrypt is here simple user of cryptoAPI,
so it depends on the module autoloading.
(Better ask on kernel crypto list http://vger.kernel.org/vger-lists.html#linux-crypto )

Milan

  reply	other threads:[~2011-03-13 13:47 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 [this message]
2011-03-13 15:23   ` Maciej Pilichowski
2011-03-13 18:29     ` Milan Broz
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=4D7CCAF5.3050903@redhat.com \
    --to=mbroz@redhat.com \
    --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.