[dm-crypt] luksAddKey successful but not working
leamhall at gmail.com
Thu May 30 02:56:30 CEST 2013
So what I'm seeing is an error "No key available with this passphrase".
What makes this odd is that there are two boxes; one build with a file
system encrypted and the other adding it afterwards. Both have the same
~/keyfile. The manually built system won't read the keyfile on boot and
drops the box into "fix your filesystem" mode. The "encrypted on install"
box works just fine.They are pretty much build from the same OS version,
though the bad one has more packages.
Any ideas on how to trouble-shoot this?
On Wed, May 22, 2013 at 11:36 AM, leam hall <leamhall at gmail.com> wrote:
> I have a support ticket with RH open now. So far I am not sure it is a
> bug. It may well just be my misunderstanding. If it does turn out to be a
> bug I will file it.
> On Wed, May 22, 2013 at 11:28 AM, Milan Broz <gmazyland at gmail.com> wrote:
>> 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
>> to rebase there to a new version.
>> You can create a bug requesting to fix this issue in RH bugzilla though...
>> dm-crypt mailing list
>> dm-crypt at saout.de
> Mind on a Mission <http://leamhall.blogspot.com/>
Mind on a Mission <http://leamhall.blogspot.com/>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the dm-crypt