From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] luksAddKey successful but not working
Date: Wed, 22 May 2013 16:33:45 +0200 [thread overview]
Message-ID: <20130522143345.GB26551@tansi.org> (raw)
In-Reply-To: <CACv9p5qPY9Q+=eW7-zVsuGsp3ryxRfxFujNS4PgRocpsqM=D5A@mail.gmail.com>
A look into the man-page of cryptsetup shows that luksAddKey does
not write the key-file, but reads it. I am surprised though that
cryptsetup does not complain that the file is missing. With my
system (cryptsetup 1.6.0) it does:
# cryptsetup luksAddKey /dev/loop0 keyfile
Enter any passphrase:
Failed to open key file. <---
#
Have you created "keyfile" before? If so, you just added the empty
passphrase to your device, something you probably do not want to do.
Arno
On Wed, May 22, 2013 at 08:50:22AM -0400, leam hall wrote:
> Help! I've nearly broken my desk banging my head against this problem. I am
> using Red Hat 5.9 base install and trying to set the LUKS volume to come
> on-line on boot.
>
> The volume can be manually mounted. However, when I try to create the key
> file it becomes a 0 length file and does not work when the system boots.
>
> cryptsetup luksAddKey /dev/sda2 keyfile
> Enter any LUKS passphrase:
> Verify passphrase:
> key slot 0 unlocked.
> Command successful.
>
>
> ls -lart keyfile
> -rw------- 1 root root 0 May 22 08:42 keyfile
>
>
> cat /etc/crypttab
> luks /dev/sda2 /root/keyfile luks
>
>
> This is probably operator error but I'm not sure where to look. Any help
> appreciated!
>
> Leam
>
>
>
> --
> Mind on a Mission <http://leamhall.blogspot.com/>
> _______________________________________________
> 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: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
There are two ways of constructing a software design: One way is to make it
so simple that there are obviously no deficiencies, and the other way is to
make it so complicated that there are no obvious deficiencies. The first
method is far more difficult. --Tony Hoare
next prev parent reply other threads:[~2013-05-22 14:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 12:50 [dm-crypt] luksAddKey successful but not working leam hall
2013-05-22 14:33 ` Arno Wagner [this message]
2013-05-22 14:48 ` leam hall
2013-05-22 15:00 ` Arno Wagner
2013-05-22 15:28 ` Milan Broz
2013-05-22 15:36 ` leam hall
2013-05-30 0:56 ` leam hall
2013-05-30 1:10 ` Arno Wagner
2013-05-31 14:09 ` leam hall
2013-05-31 14:55 ` leam hall
2013-05-31 15:53 ` Arno Wagner
2013-06-06 17:41 ` leam hall
2013-06-26 14:12 ` leam hall
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=20130522143345.GB26551@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox