From: Eric Bauman <baumane@livejournal.dk>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] LUKS and LVM
Date: Sun, 20 Feb 2011 01:01:18 +1100 [thread overview]
Message-ID: <ijoifg$8ns$1@dough.gmane.org> (raw)
In-Reply-To: <20110218200718.GA12395@tansi.org>
On 19/02/2011, Arno Wagner wrote:
>Also, knowing were the encrypted
> data is does not help the attacker, unless he/she can repeatedly
> access the computer. In that case, all is luikely lost anyways.
Forgive my ignorance, some sources say suggest randomising the disk
before creating a container so that it's not possible to determine what
is data and what is garbage. So I assumed the visible LVM header would
reduce some of this benefit. Is there merit to this disk randomisation
or does it just sound good but do nothing, spread by misinformed people
such as myself? :)
Thanks,
Eric
next prev parent reply other threads:[~2011-02-19 14:01 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
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 [this message]
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='ijoifg$8ns$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 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.