All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: sven@whgl.uni-frankfurt.de, dm-crypt@saout.de
Subject: Re: [dm-crypt] cryptsetup upgrade to 1.6.x unlocking problem in initramfs
Date: Thu, 04 Sep 2014 09:24:01 +0200	[thread overview]
Message-ID: <54081391.6000003@gmail.com> (raw)
In-Reply-To: <3ff26a70ae9179ea3c37012459998cf4.squirrel@ssl.verfeiert.org>

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

  reply	other threads:[~2014-09-04  7:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-01 19:32 [dm-crypt] cryptsetup upgrade to 1.6.x unlocking problem in initramfs Sven Eschenberg
2014-09-01 20:00 ` Milan Broz
2014-09-01 20:12   ` Sven Eschenberg
2014-09-01 20:41     ` Milan Broz
2014-09-01 21:35       ` Sven Eschenberg
2014-09-03 16:56         ` Milan Broz
2014-09-03 21:03           ` Sven Eschenberg
2014-09-04  7:24             ` Milan Broz [this message]
2014-09-04 22:54               ` Sven Eschenberg
2014-09-05 15:29                 ` Milan Broz
2014-09-05 22:23                   ` Arno Wagner
2014-09-05 22:39                   ` Sven Eschenberg

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=54081391.6000003@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=dm-crypt@saout.de \
    --cc=sven@whgl.uni-frankfurt.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.