DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <mbroz@redhat.com>
To: Si St <sigbj-st@operamail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] "ERROR:apitest failed" after make check cryptsetup 1.1.0
Date: Tue, 27 Apr 2010 21:38:11 +0200	[thread overview]
Message-ID: <4BD73D23.2080903@redhat.com> (raw)
In-Reply-To: <20100427191327.C904E77B1DF@c-in3ws--03-01.sv2.lotusliveops.com>

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, &params)
> 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

  reply	other threads:[~2010-04-27 19:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-27 19:13 [dm-crypt] "ERROR:apitest failed" after make check cryptsetup 1.1.0 Si St
2010-04-27 19:38 ` Milan Broz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-04-28  9:13 Si St
2010-04-28 10:17 ` Milan Broz
2010-04-28 15:56 Si St
2010-04-28 16:07 ` Felix Blanke
2010-04-28 16:09 Si St
2010-04-29 17:10 ` Milan Broz
2010-04-28 16:18 Si St
2010-04-30  9:47 Si St

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=4BD73D23.2080903@redhat.com \
    --to=mbroz@redhat.com \
    --cc=dm-crypt@saout.de \
    --cc=sigbj-st@operamail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox