Okay, progress. And yeah, I dwaddled on reading the FAQ. :(
I think this works, the volume mounts on boot. However, if I use isLuks on the /dev/mapper/<volume> it is not. If I use it on the underlying partition (/dev/sdc1) it gives no response and "echo $?" gives a 0.
On Fri, May 31, 2013 at 10:09 AM, leam hall <leamhall@xxxxxxxxx> wrote:
I can build a new box without an encrypted volume, build the volume, and have the server ask for the password on boot. What is currently failing is reading the keyfile so that it doesn't ask for a password. What part of the program/process deals with that?
Thanks!
LeamOn Wed, May 22, 2013 at 11:36 AM, leam hall <leamhall@xxxxxxxxx> 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.Thanks!
LeamOn Wed, May 22, 2013 at 11:28 AM, Milan Broz <gmazyland@xxxxxxxxx> wrote:
On 05/22/2013 04:33 PM, Arno Wagner wrote:RHEL5 has very old cryptsetup (based on 1.0.3 version) and it is impossible
> 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. <---
> #
to rebase there to a new version.
You can create a bug requesting to fix this issue in RH bugzilla though...
Milan
_______________________________________________
dm-crypt mailing list
dm-crypt@xxxxxxxx
http://www.saout.de/mailman/listinfo/dm-crypt
--
--
_______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
