From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mbroz@redhat.com>
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
 by mail.saout.de (Postfix) with ESMTP
 for <dm-crypt@saout.de>; Sun, 13 Mar 2011 14:47:37 +0100 (CET)
Received: from int-mx01.intmail.prod.int.phx2.redhat.com
 (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11])
 by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p2DDlZUi010730
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK)
 for <dm-crypt@saout.de>; Sun, 13 Mar 2011 09:47:36 -0400
Received: from [10.36.8.58] (vpn2-8-58.ams2.redhat.com [10.36.8.58])
 by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id
 p2DDlYfm008393
 for <dm-crypt@saout.de>; Sun, 13 Mar 2011 09:47:35 -0400
Message-ID: <4D7CCAF5.3050903@redhat.com>
Date: Sun, 13 Mar 2011 14:47:33 +0100
From: Milan Broz <mbroz@redhat.com>
MIME-Version: 1.0
References: <201103131045.26845.bluedzins@wp.pl>
 <20110313105332.GA6745@fancy-poultry.org>
In-Reply-To: <20110313105332.GA6745@fancy-poultry.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] How to activate hash module?
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: dm-crypt@saout.de

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