From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx4.wp.pl (mx4.wp.pl [212.77.101.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Sun, 13 Mar 2011 19:56:38 +0100 (CET) Received: from 178-36-65-80.adsl.inetia.pl (HELO [192.168.1.2]) (bluedzins@[178.36.65.80]) (envelope-sender ) by smtp.wp.pl (WP-SMTPD) with AES256-SHA encrypted SMTP for ; 13 Mar 2011 19:56:36 +0100 From: Maciej Pilichowski Date: Sun, 13 Mar 2011 19:58:30 +0100 References: <201103131045.26845.bluedzins@wp.pl> <201103131623.19883.bluedzins@wp.pl> <4D7D0D12.2020303@redhat.com> In-Reply-To: <4D7D0D12.2020303@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <201103131958.30968.bluedzins@wp.pl> Subject: Re: [dm-crypt] How to activate hash module? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de Hello, On Sunday 13 March 2011 19:29:38 Milan Broz wrote: > > Code 22: Requested LUKS hash ripemd320 is not supported. > > ...and you will be surprised with answer :) I am! :-( > 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. You are 100% correct and thank you million times for help! The sad fact is I am example of blindly trusting other parties, that something actually works, when it does not. > (Hash switch was useful only for plain mapping for passphrase > hashing.) If I may ask a bit off-topic question: * you wrote "was", so now it is useful in general? * what do you mean by "plain mapping"? (I googled with no success) Once again, thank you very much, back to upgrading to OS11.4 ;-) Kind regards,