From: Heinz Diehl <htd@fancy-poultry.org>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] cryptsetup not working under 3.6 - regression from 3.4?
Date: Sun, 21 Oct 2012 12:00:15 +0200 [thread overview]
Message-ID: <20121021100015.GA2062@fancy-poultry.org> (raw)
In-Reply-To: <50830D33.5050807@ursulin.net>
On 21.10.2012, Tvrtko Ursulin wrote:
> # cryptsetup --key-file=- luksOpen /luks.file target
> Enter passphrase:
> device-mapper: reload ioctl on failed: No such file or directory
> Failed to setup dm-crypt key mapping for device /dev/loop0.
> Check that kernel supports aes-cbc-essiv:sha256 cipher (check syslog for
> more info).
I bet you miss some of the neccessary crypto-stuff in your .config.
I tested your case and have no problems:
[root@wildsau htd]# uname -a
Linux wildsau.fritha.org 3.6.3-rc1 #1 SMP PREEMPT Sat Oct 20 18:57:04 CEST 2012 x86_64 x86_64 x86_64 GNU/Linux
[root@wildsau htd]# cryptsetup luksDump /dev/loop0
LUKS header information for /dev/loop0
Version: 1
Cipher name: aes
Cipher mode: cbc-essiv:sha256
Hash spec: sha1
Payload offset: 4096
MK bits: 256
MK digest: 0e 1b a2 0a c3 db f0 16 27 df fb 2a ea e8 2e a9 15 ec f9 6e
MK salt: c6 56 f1 f8 38 4a 69 81 42 91 ce e1 3c b4 36 b6
05 9c c1 ee 1a a2 21 ce ec a8 ea f9 84 cf 3e 28
MK iterations: 42125
UUID: 5b894353-1b52-40fa-bc59-4ce5b3795894
Key Slot 0: ENABLED
Iterations: 168948
Salt: 77 f7 f5 1b 7e 8c ea 18 1f de fd 1c 9a fd 96 9d
f3 6e 76 9f 9d 5f 97 b2 72 9e 83 ff 59 13 1e a9
Key material offset: 8
AF stripes: 4000
Key Slot 1: DISABLED
prev parent reply other threads:[~2012-10-21 10:00 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-20 20:44 [dm-crypt] cryptsetup not working under 3.6 - regression from 3.4? Tvrtko Ursulin
2012-10-20 20:44 ` Tvrtko Ursulin
2012-10-21 9:53 ` [dm-crypt] " Milan Broz
2012-10-21 12:03 ` Tvrtko Ursulin
2012-10-21 12:20 ` Zdenek Kaspar
2012-10-21 12:36 ` Tvrtko Ursulin
2012-10-21 12:36 ` Tvrtko Ursulin
2012-10-21 19:29 ` [dm-crypt] " Milan Broz
2012-10-21 19:29 ` Milan Broz
2012-10-21 20:03 ` [dm-crypt] " Tvrtko Ursulin
2012-10-21 20:03 ` Tvrtko Ursulin
2012-10-22 14:27 ` [dm-crypt] " Ondrej Kozina
2012-10-29 19:31 ` Tvrtko Ursulin
2012-10-29 19:31 ` Tvrtko Ursulin
2012-10-29 19:47 ` [dm-crypt] " Milan Broz
2012-10-29 19:47 ` Milan Broz
2012-10-29 20:14 ` Tvrtko Ursulin
2012-10-29 20:14 ` Tvrtko Ursulin
2012-10-29 20:45 ` [dm-crypt] cryptsetup not working under 3.6 - RT patch set seem to break it Tvrtko Ursulin
2012-10-29 20:45 ` Tvrtko Ursulin
2012-10-29 20:45 ` Tvrtko Ursulin
2012-10-29 23:51 ` [dm-crypt] " Thomas Gleixner
2012-10-29 23:51 ` Thomas Gleixner
2012-10-30 9:40 ` Uwe Kleine-König
2012-10-30 9:40 ` Uwe Kleine-König
2012-10-30 9:55 ` Milan Broz
2012-10-30 9:55 ` Milan Broz
2012-10-30 9:55 ` Milan Broz
2012-10-30 15:27 ` [dm-crypt] [PATCH] Fix crypto api init for 3.6.4-rt10 Milan Broz
2012-10-30 15:27 ` Milan Broz
2012-10-30 17:57 ` [dm-crypt] " Thomas Gleixner
2012-10-30 17:57 ` Thomas Gleixner
2012-10-30 20:35 ` [dm-crypt] " Uwe Kleine-König
2012-10-30 20:35 ` Uwe Kleine-König
2012-10-30 20:35 ` Uwe Kleine-König
2012-10-30 18:24 ` [dm-crypt] " Tvrtko Ursulin
2012-10-30 18:24 ` Tvrtko Ursulin
2012-10-29 20:48 ` [dm-crypt] cryptsetup not working under 3.6 - regression from 3.4? Milan Broz
2012-10-29 20:48 ` Milan Broz
2012-10-21 10:00 ` Heinz Diehl [this message]
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=20121021100015.GA2062@fancy-poultry.org \
--to=htd@fancy-poultry.org \
--cc=dm-crypt@saout.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.