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 19:29:41 +0100 (CET)
Message-ID: <4D7D0D12.2020303@redhat.com>
Date: Sun, 13 Mar 2011 19:29:38 +0100
From: Milan Broz <mbroz@redhat.com>
MIME-Version: 1.0
References: <201103131045.26845.bluedzins@wp.pl>
 <20110313105332.GA6745@fancy-poultry.org>
 <201103131623.19883.bluedzins@wp.pl>
In-Reply-To: <201103131623.19883.bluedzins@wp.pl>
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: Maciej Pilichowski <bluedzins@wp.pl>
Cc: dm-crypt@saout.de


>> 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