From: Milan Broz <gmazyland@gmail.com>
To: Johannes Ernst <johannes.ernst@gmail.com>
Cc: dm-crypt@saout.de, Lars Winterfeld <lars.winterfeld@tu-ilmenau.de>
Subject: Re: [dm-crypt] cryptsetup problem on Raspberry Pi 2 w 512bit key-size (works on Raspberry Pi 1, x86_64, 256bit)
Date: Sun, 22 Feb 2015 21:20:10 +0100 [thread overview]
Message-ID: <54EA39FA.7010408@gmail.com> (raw)
In-Reply-To: <EE112BA4-BDD8-4CB3-BD7B-BDA984D15089@gmail.com>
On 02/22/2015 08:40 PM, Johannes Ernst wrote:
>> (If us use other hash it works even on Pi? Try sha1 and sha256 at least.)
>
> It appears independent of the hash involved: I tried sha1, sha256 in addition to the original sha256. The behavior is the same:
> 1. cryptsetup open … does not open
> 2. cryptsetup open —debug opens on the second attempt to put the password in.
ok, this is really strange.
One (random) guess from the log:
> # Using userspace crypto wrapper to access keyslot area.
it means that code is using kernel userspace crypto
(and cryptsetup already revealed at least two problems there...)
Could you try it without it? (Code should fallback to old dmcrypt temporary devices mode).
You can do it either by
- disabling/blacklisting kernel modules which provides it: af_alg.ko and algif_skcipher.ko
(or disable CRYPTO_USER_API, CRYPTO_USER_API_SKCIPHER when compiling kernel)
- try to run older cryptsetup (at least 1.6.4 or older)
I am afraid I cannot help more here without reproducing it...
(Is it RPI2 only issue or anyone see it on other ARM device?)
Milan
next prev parent reply other threads:[~2015-02-22 20:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 21:37 [dm-crypt] cryptsetup problem on Raspberry Pi 2 w 512bit key-size (works on Raspberry Pi 1, x86_64, 256bit) Johannes Ernst
2015-02-20 22:25 ` Lars Winterfeld
2015-02-20 22:59 ` Johannes Ernst
2015-02-21 6:53 ` Milan Broz
2015-02-22 19:29 ` Johannes Ernst
2015-02-22 19:36 ` Johannes Ernst
2015-02-22 19:40 ` Johannes Ernst
2015-02-22 20:20 ` Milan Broz [this message]
2015-02-23 18:44 ` Johannes Ernst
2015-02-23 19:03 ` Milan Broz
2015-02-23 23:02 ` Johannes Ernst
2015-02-28 0:48 ` Milan Broz
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=54EA39FA.7010408@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-crypt@saout.de \
--cc=johannes.ernst@gmail.com \
--cc=lars.winterfeld@tu-ilmenau.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.