From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gmazyland@gmail.com>
Received: from mail-la0-x233.google.com (mail-la0-x233.google.com
 [IPv6:2a00:1450:4010:c03::233])
 (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>; Thu,  4 Sep 2014 09:24:05 +0200 (CEST)
Received: by mail-la0-f51.google.com with SMTP id gl10so11118540lab.38
 for <dm-crypt@saout.de>; Thu, 04 Sep 2014 00:24:04 -0700 (PDT)
Message-ID: <54081391.6000003@gmail.com>
Date: Thu, 04 Sep 2014 09:24:01 +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>
 <5407482C.1060902@gmail.com>
 <3ff26a70ae9179ea3c37012459998cf4.squirrel@ssl.verfeiert.org>
In-Reply-To: <3ff26a70ae9179ea3c37012459998cf4.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/03/2014 11:03 PM, Sven Eschenberg wrote:
> Will mail that in a bit directly to you. I looked at the strace again and
> realized the following:
> the call to initialize the backend with the fixed values in sockaddr_alg
> (AF_ALG,"hash","sha1") obviously succeeds, the one after entering the
> passphrase, which is filled with AF_ALG, "hash", and the hashname, which
> should be sha1 again, seems to fail.

I tried your config (just added hw drivers so it boots on my VM)
and for my non-initram i386 system it works.

The only module it requires to load (all other are compiled in) is hmac,
so try CONFIG_CRYPTO_HMAC=y or check it is in initramfs.

And obviously, removing this module so kernel cannot find it causes
...
socket(PF_ALG, SOCK_SEQPACKET, 0)       = 6
bind(6, {sa_family=AF_ALG, sa_data="hash\0\0\0\0\0\0\0\0\0\0"}, 88) = -1 ENOENT (No such file or directory)
                                = 0
I will probably try to add some better debug messages here
(but you did not send me --debug output anyway :-)

Milan