From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] LUKS and LVM
Date: Fri, 18 Feb 2011 18:33:02 +0100 [thread overview]
Message-ID: <20110218173302.GA9234@tansi.org> (raw)
In-Reply-To: <ijm7bb$orl$1@dough.gmane.org>
On Sat, Feb 19, 2011 at 03:39:07AM +1100, Eric Bauman wrote:
> Hi,
>
> When using LVM with LUKS, is it more secure to:
> 1 - have a single container containing LVM, or
> 2 - LVM containing multiple containers?
Technologically, security is the same. Reliability is
lower on (2) as you have more headers you can damage and
lose.
As with RAID, encryption should sit on top, not somewhere
in between.
With regard to interface and usability (allways _very_ important
in security!), (1) is a lot better, since (2) requires you
to unlock multiple containers and keep multiple passowrds or
enter the same password multiple times.
That makes option (1) the thing to do and option (2)
a curiosity that violates a number of principles, among them
simplicity, crypto as last/highest layer below the filesystem,
leas amount of credentials, least exposure of the credentials.
> 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.
I don't follow. That encrypted data is present is obvious from
the LUKS header. What is in the container(s) is as opaque in
(1) as it is in (2), given that cryptographically strong
randomness is used for the overwrite (I use plain dm-crypt
with a random password and overwrite with conventional,
mt19997-generated randomness).
Arno
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name
GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F
----
Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
next prev parent reply other threads:[~2011-02-18 17:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 16:39 [dm-crypt] LUKS and LVM Eric Bauman
2011-02-18 17:33 ` Arno Wagner [this message]
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=20110218173302.GA9234@tansi.org \
--to=arno@wagner.name \
--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