From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by mail.saout.de (Postfix) with ESMTP for ; Tue, 27 Apr 2010 21:38:16 +0200 (CEST) Message-ID: <4BD73D23.2080903@redhat.com> Date: Tue, 27 Apr 2010 21:38:11 +0200 From: Milan Broz MIME-Version: 1.0 References: <20100427191327.C904E77B1DF@c-in3ws--03-01.sv2.lotusliveops.com> In-Reply-To: <20100427191327.C904E77B1DF@c-in3ws--03-01.sv2.lotusliveops.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] "ERROR:apitest failed" after make check cryptsetup 1.1.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Si St Cc: dm-crypt@saout.de On 04/27/2010 09:13 PM, Si St wrote: > NonFIPSAlg: Crypto is properly initialised in format > [(success),NonFIPSAlg:691] crypt_init(&cd, DEVICE_2) > [(success),NonFIPSAlg:692] crypt_format(cd, CRYPT_LUKS1, cipher, cipher_mode, NULL, key, key_size, ¶ms) > FAIL line 692 [NonFIPSAlg]: code -22, Not compatible PBKDF2 options (using hash algorithm whirlpool). That's test that gcrypt is properly initialised, strange it fails, seems like it uses wrong libcryptsetup... can you try svn snapshot first - does it work? But the tests are not properly integrated yet in Makefile/autoconf, I wrote them to verify new library API/old calls compatibility but not finished integration in autoconf. (There are hardcoded loop names etc., another old tests are directly in makefile run by "cd tests; mate test; ...) Milan