DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Anton Mitterer <calestyo@scientia.net>
To: dm-crypt@saout.de
Subject: [dm-crypt] security concerns with RAID on top of dmcrpyt and with mulitple devices with the same key slot key?
Date: Fri, 03 Jun 2016 01:47:49 +0200	[thread overview]
Message-ID: <1464911269.14592.52.camel@scientia.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]

Hey.

I just wondered the following:
- Are there any security concerns (e.g. simplified statistical attacks
  or whatever), when one places a RAID (e.g. btrfs RAID or MD RAID) on
  top of dmcrypt devices?
- Are there any security concerns when different dm-crypt devices (with
  different master-keys), e.g. ones that form a RAID as above, are
  created with the same keyslot passphrase/key?
  (Of course apart the obvious one, that one can decrypt all with the
  single key)?

If so, does it depend on the cipher/mode/etc? I'd use aes-xts-plain64.

I wouldn't think so, but just for confirmation...



Perhaps in addition:
As you can imagine the setup I'd like to do is e.g. something like n
physical devices, each holding a LUKS container (with different master
key, but all with the same keyslot key), on top of them some btrfs
RAID5/6 (should that ever get stable before I die ;-) )...
Probably I'll do LVM between dmcrypt and btrfs, because I'd actually
want to create two independent btrfs filesystems on top of dmcrypt.

Any performance or stability issues with such setup?


Thanks,
Chris.

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5930 bytes --]

             reply	other threads:[~2016-06-02 23:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-02 23:47 Christoph Anton Mitterer [this message]
2016-06-03  2:41 ` [dm-crypt] security concerns with RAID on top of dmcrpyt and with mulitple devices with the same key slot key? David Christensen
2016-06-03  3:14   ` Christoph Anton Mitterer
2016-06-03  4:36     ` David Christensen

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=1464911269.14592.52.camel@scientia.net \
    --to=calestyo@scientia.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox