From: Eric Bauman <baumane@livejournal.dk>
To: dm-crypt@saout.de
Subject: [dm-crypt] LUKS and LVM
Date: Sat, 19 Feb 2011 03:39:07 +1100 [thread overview]
Message-ID: <ijm7bb$orl$1@dough.gmane.org> (raw)
Hi,
When using LVM with LUKS, is it more secure to:
1 - have a single container containing LVM, or
2 - LVM containing multiple containers?
I typically randomise my block device before creating a LUKS container
on it. Option 2 would seem to reduce the effectiveness of this because
LVM will give clues to where real data might be.
Thoughts?
Thanks,
Eric
next reply other threads:[~2011-02-18 17:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 16:39 Eric Bauman [this message]
2011-02-18 17:33 ` [dm-crypt] LUKS and LVM Arno Wagner
2011-02-18 17:53 ` Eric Bauman
2011-02-18 19:57 ` Milan Broz
2011-02-18 20:07 ` Arno Wagner
2011-02-19 14:01 ` Eric Bauman
2011-02-19 14:52 ` Arno Wagner
2011-02-19 16:46 ` Nicolas Bock
2011-02-19 17:10 ` Milan Broz
2011-02-19 18:17 ` Jonas Meurer
2011-02-19 19:11 ` Nicolas Bock
2011-02-19 19:10 ` Arno Wagner
2011-02-19 19:08 ` Arno Wagner
2011-02-19 19:12 ` Nicolas Bock
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='ijm7bb$orl$1@dough.gmane.org' \
--to=baumane@livejournal.dk \
--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