From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pz0-f50.google.com (mail-pz0-f50.google.com [209.85.210.50]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Sat, 19 Feb 2011 17:46:11 +0100 (CET) Received: by pzk27 with SMTP id 27so915456pzk.37 for ; Sat, 19 Feb 2011 08:46:09 -0800 (PST) Message-ID: <4D5FF3CC.6010804@gmail.com> Date: Sat, 19 Feb 2011 09:46:04 -0700 From: Nicolas Bock MIME-Version: 1.0 References: <20110218173302.GA9234@tansi.org> <20110218200718.GA12395@tansi.org> In-Reply-To: <20110218200718.GA12395@tansi.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] LUKS and LVM List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/18/11 13:07, Arno Wagner wrote: > (I use plain dm-crypt >>> with a random password and overwrite with conventional, >>> mt19997-generated randomness). Why use random data to overwrite? Shouldn't /dev/zero be enough since the crypto should produce good randomness on disk? nick -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1f88wACgkQf15tZKyRylI/HACdHUaYyhGQf9bmBNaoLUSjwTuJ okkAoI0DPaJBq76g6uz/UZpWCw5p/gBN =8V+K -----END PGP SIGNATURE-----