All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Christensen <dpchrist@holgerdanske.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Debian 7.10 random key swap Device /dev/sda2 is not a valid LUKS device.
Date: Wed, 6 Apr 2016 12:35:35 -0700	[thread overview]
Message-ID: <57056507.6020907@holgerdanske.com> (raw)
In-Reply-To: <20160406105535.GG9664@yeono.kjorling.se>

On 04/06/2016 03:55 AM, Michael Kjörling wrote:
> On 5 Apr 2016 21:25 -0700, from dpchrist@holgerdanske.com (David Christensen):
>> # grep sda2 /etc/crypttab
>> sda2_crypt /dev/sda2                                 /dev/urandom
>> cipher=aes-xts-plain64,size=256,swap
>
> Since you don't have the "luks" option, Debian does not treat this as
> a LUKS device. So when cryptsetup claims that /dev/sda2 "is not a
> valid LUKS device" it is quite correct.
>

Thanks for the information.


So, RTFM 'crypttab':  at boot time /sbin/cryptdisks_start will create a 
plain dm-crypt device with target name 'sda2_crypt' 
(/dev/mapper/sda2_crypt) from source device /dev/sda2 with a 256-bit key 
(option 'size') from file /dev/urandom and with cipher aes-xts-plain64 
(option 'cipher'), and then run /sbin/mkswap on the created device 
(option 'swap') (?).


And, as plain dm-crypt devices do not have a LUKS header, 
'luksHeaderBackup' has nothing to back up and the error message I'm 
seeing is expected and correct (?).


David

  reply	other threads:[~2016-04-06 19:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-06  4:25 [dm-crypt] Debian 7.10 random key swap Device /dev/sda2 is not a valid LUKS device David Christensen
2016-04-06  5:38 ` Milan Broz
2016-04-06  5:59   ` David Christensen
2016-04-06  6:37     ` Milan Broz
2016-04-06 10:55 ` Michael Kjörling
2016-04-06 19:35   ` David Christensen [this message]
2016-04-06 20:26     ` Sven Eschenberg
2016-04-06 23:06       ` David Christensen
2016-04-07  9:39       ` Arno Wagner
2016-04-07  9:46         ` Arno Wagner

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=57056507.6020907@holgerdanske.com \
    --to=dpchrist@holgerdanske.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.