On 03/08/2016 04:36 PM, lejeczek wrote:
On 08/03/16 14:14, Ondrej Kozina wrote:
On 03/08/2016 03:02 PM, lejeczek wrote:
superb, thanks chaps,
on keyfiles, would you know why this:
cryptsetup luksOpen /dev/h300Int1/0 h300Int1.0_crypt
/etc/crypttab.key --keyfile-offset 12
IIUC it seems like missing -d/--key-file option in front
of "/etc/crypttab.key" string. Well it also depends on
actual content of your /etc/crypttab.key file. Does it
really contain backup of your keyslot passphrase (human
readable text data)? Or does it contain volume key for
your luks device (usually looks like binary data, bunch of
random bytes that really should not be human readable:))
Regards
Ondrej
many thanks Onrej,
it seems I got it completely wrong, the concept of it, I
thought the keyfile is pure randomness and I just simply
pick up a chunk of it with the help of offest.
But why then it works fine without offset, with no
passphrase in keyfile at any time?
Ok, let's return back to the origin. How did you create your encrypted
device? Did you use cryptsetup luksFormat command? If so what options
did you pass to it? In a default mode luksFormat command generates a
random volume key for the device but also asks you for a passphrase. The
passphrase is later used in cryptsetup open command when activating the
encrypted device.
Anyway, if you have further questions this is proper list for
cryptsetup/dm-crypt discussions:
http://www.saout.de/mailman/listinfo/dm-crypt
O.
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
