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: Wed, 03 Sep 2014 18:56:12 +0200 [thread overview]
Message-ID: <5407482C.1060902@gmail.com> (raw)
In-Reply-To: <57348c6a4168767613f999ddabe9a54f.squirrel@ssl.verfeiert.org>
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
next prev parent reply other threads:[~2014-09-03 16:56 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 [this message]
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=5407482C.1060902@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.