From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gmazyland@gmail.com>
Received: from mail-lb0-x22d.google.com (mail-lb0-x22d.google.com
 [IPv6:2a00:1450:4010:c04::22d])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mail.server123.net (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Wed,  3 Sep 2014 18:56:16 +0200 (CEST)
Received: by mail-lb0-f173.google.com with SMTP id c11so9928030lbj.18
 for <dm-crypt@saout.de>; Wed, 03 Sep 2014 09:56:15 -0700 (PDT)
Message-ID: <5407482C.1060902@gmail.com>
Date: Wed, 03 Sep 2014 18:56:12 +0200
From: Milan Broz <gmazyland@gmail.com>
MIME-Version: 1.0
References: <27d5e048ef3f17501e9e92019b4c7643.squirrel@ssl.verfeiert.org>
 <5404D045.5020002@gmail.com>
 <8eb220aa5096641f9144b1128d117ed4.squirrel@ssl.verfeiert.org>
 <5404DA01.2050507@gmail.com>
 <57348c6a4168767613f999ddabe9a54f.squirrel@ssl.verfeiert.org>
In-Reply-To: <57348c6a4168767613f999ddabe9a54f.squirrel@ssl.verfeiert.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] cryptsetup upgrade to 1.6.x unlocking problem in
	initramfs
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: sven@whgl.uni-frankfurt.de, dm-crypt@saout.de

On 09/01/2014 11:35 PM, Sven Eschenberg wrote:
> Here's the CRYPTO config of the kernel that works with old cryptsetup:
> 
> CONFIG_CRYPTO=y
> CONFIG_CRYPTO_ALGAPI=y
> CONFIG_CRYPTO_ALGAPI2=y
> CONFIG_CRYPTO_AEAD2=y
> CONFIG_CRYPTO_BLKCIPHER=y
> CONFIG_CRYPTO_BLKCIPHER2=y
> CONFIG_CRYPTO_HASH=y
> CONFIG_CRYPTO_HASH2=y
> CONFIG_CRYPTO_RNG2=y
> CONFIG_CRYPTO_PCOMP2=y
> CONFIG_CRYPTO_MANAGER=y
> CONFIG_CRYPTO_MANAGER2=y
> CONFIG_CRYPTO_GF128MUL=y
> CONFIG_CRYPTO_WORKQUEUE=y
> CONFIG_CRYPTO_CBC=y
> CONFIG_CRYPTO_XTS=y
> CONFIG_CRYPTO_RMD160=y
> CONFIG_CRYPTO_SHA1=y
> CONFIG_CRYPTO_SHA256=y
> CONFIG_CRYPTO_AES=y
> CONFIG_CRYPTO_AES_586=y
> -----
> What I added to get to the passphrase for current cryptsetup is:
> CONFIG_CRYPTO_ANSI_CPRNG=y
> CONFIG_CRYPTO_USER_API=y <= AF_ALGO
> CONFIG_CRYPTO_USER_API_HASH=y
> CONFIG_CRYPTO_USER_API_SKCIPHER=y
> ----
> 
> The Volume is AES-XTS-plain and the hashspec sha1
> 
> I can't see what might be missing ...

If you can send which exact kernel version it is and full .config,
which fails I can try to reproduce it.

Thanks,
Milan