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: Mon, 01 Sep 2014 22:41:37 +0200	[thread overview]
Message-ID: <5404DA01.2050507@gmail.com> (raw)
In-Reply-To: <8eb220aa5096641f9144b1128d117ed4.squirrel@ssl.verfeiert.org>

On 09/01/2014 10:12 PM, Sven Eschenberg wrote:
> On Mon, September 1, 2014 22:00, Milan Broz wrote:
>> Which exact version you are using? Be sure that you have the last 1.6.6
>> where I fixed some problems related to crypto API interface.
> 
> Okay, I am using 1.6.4, will upgrade it and check again...

ok, then it is different issue I thought (there was a change
in 1.6.5 which caused a lot of similar issues), see below.

Anyway, please try 1.6.6. as well - there was some related changes.

>> Can you post output with added --debug of command which fails?
>>
>> If you are compiling cryptsetup yourself, which crypto backend are you
>> using?
>> (If it is kernel API, then kernel must have required support, AF_ALG
>> API and all relevant crypto modules.)
> 
> Always used the kernel backend. I reused the kernel config (just minor
> upgrade) which worked with the old cryptsetup.

So if you use kernel backend you simply must have kernel with the AF_ALG interface.

Also be sure you have SHA1 and hash used in your LUKS (if differs from SHA1).
(SHA1 is mandatory for LUKS support, crypto backend also uses it to check
that API is working -  I did not find other reliable way...)

Anyway, I would say that it is not problem in cryptsetup but that some required
kernel module is missing (it can be some dependence like cipher mode helper
or cryptomgr...)

Milan

  reply	other threads:[~2014-09-01 20:41 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 [this message]
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
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=5404DA01.2050507@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.