From: Milan Broz <gmazyland@gmail.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] luksAddKey successful but not working
Date: Wed, 22 May 2013 17:28:27 +0200 [thread overview]
Message-ID: <519CE41B.5030205@gmail.com> (raw)
In-Reply-To: <20130522143345.GB26551@tansi.org>
On 05/22/2013 04:33 PM, Arno Wagner wrote:
> 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. <---
> #
RHEL5 has very old cryptsetup (based on 1.0.3 version) and it is impossible
to rebase there to a new version.
You can create a bug requesting to fix this issue in RH bugzilla though...
Milan
next prev parent reply other threads:[~2013-05-22 15:28 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
2013-05-22 14:48 ` leam hall
2013-05-22 15:00 ` Arno Wagner
2013-05-22 15:28 ` Milan Broz [this message]
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=519CE41B.5030205@gmail.com \
--to=gmazyland@gmail.com \
--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.