From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Newbie question --key-file
Date: Fri, 26 Oct 2012 19:53:27 +0200 [thread overview]
Message-ID: <20121026175327.GA14117@tansi.org> (raw)
In-Reply-To: <508ABC36.7060407@gmail.com>
On Fri, Oct 26, 2012 at 06:37:10PM +0200, Milan Broz wrote:
> > [Li, David] Can you explain a little here why key slot wasn't used?
> > Why did the luksDump or the blkid result seem to be normal?
>
> I think there are just missing internal kernel modules.
>
> Cryptsetup internally first generates master key, then writes visible header and then
> enables keyslot - and for keyslot write it requires kernel crypto modules.
> If last step fails, you end up with LUKS header without any slot enabled.
Maybe use the kernel crypto modules needed later in some
dummy operation early on?
That way you could terminate with error before the header gets
written.
Arno
> (The error reporting here is not optimal, still thinking how to get
> exact infmation from kernel.
> Anyway there is:
> "Check that kernel supports aes-cbc-essiv:sha256 cipher (check syslog for more info)."
>
> Did you check syslog?
>
> According to /proc/crypto, you have no aes module, no cbc, no sha256...
>
> Milan
>
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
>
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F
----
One of the painful things about our time is that those who feel certainty
are stupid, and those with any imagination and understanding are filled
with doubt and indecision. -- Bertrand Russell
prev parent reply other threads:[~2012-10-26 17:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 2:06 [dm-crypt] Newbie question --key-file Li, David
2012-10-26 8:26 ` Dennis Birkholz
2012-10-26 16:27 ` Li, David
2012-10-26 16:37 ` Milan Broz
2012-10-26 17:53 ` Arno Wagner [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=20121026175327.GA14117@tansi.org \
--to=arno@wagner.name \
--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.