From: Nicolas Bock <nicolasbock@gmail.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] LUKS and LVM
Date: Sat, 19 Feb 2011 12:11:12 -0700 [thread overview]
Message-ID: <4D6015D0.1090605@gmail.com> (raw)
In-Reply-To: <20110219181744.GD4287@resivo.wgnet.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02/19/11 11:17, Jonas Meurer wrote:
> Hey Milan,
>
> On 19/02/2011 Milan Broz wrote:
>> On 02/19/2011 05:46 PM, Nicolas Bock wrote:
>>> Why use random data to overwrite? Shouldn't /dev/zero be enough since
>>> the crypto should produce good randomness on disk?
>>
>> Then you can distinguish between used blocks ("random noise") and
>> unused blocks (remains zeroed).
>>
>> So filling with zero guarantees that old data are wiped, but also
>> leaks info which blocks were overwritten later.
>
> If I got Arno right, he, first setups a plain dm-crypt device for the
> to-be-encrypted partition, and then fills the encrypted device with
> random data. In this case it should be enough to fill the encrypted
> device with zeros, shouldn't it?
That's how I understood Arno's email too. The zeros will be written as
"random noise" to disk since they go through the cipher first. I could
see though that the extra paranoid would use a random source :)
nick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk1gFdAACgkQf15tZKyRylLAPwCfW0bYHV6GpOnkx4LmYm1Y4iw2
LokAn0UbYJi/uox26XTD8+sXaq6C8hG7
=yEjW
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-02-19 19:11 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
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 [this message]
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=4D6015D0.1090605@gmail.com \
--to=nicolasbock@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox