From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.8]) by mail.saout.de (Postfix) with ESMTP for ; Sun, 30 Aug 2009 14:02:38 +0200 (CEST) Received: from liesel.fancy-poultry.org (localhost [127.0.0.1]) by liesel.fancy-poultry.org (Postfix) with ESMTP id 7BF9218CDA99C for ; Sun, 30 Aug 2009 14:07:27 +0200 (CEST) Date: Sun, 30 Aug 2009 14:07:27 +0200 Message-ID: <87hbvp33pc.wl%htd@fancy-poultry.org> From: Heinz Diehl In-Reply-To: <200908291558.58894.dmcryptmailman@strokerville.com> References: <200908291558.58894.dmcryptmailman@strokerville.com> MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Subject: Re: [dm-crypt] Random fill List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de At Sat, 29 Aug 2009 15:58:58 -0400, Stroker wrote: > My question is, wouldn't the following command fill my > drives with randommess? Much more quickly than urandom? > dd if=/dev/zero of=/dev/mapper/encrypted_sdb1 Yes, with pseudorandomness just like urandom, as far as I know. > Perhaps change the key afterward, or even delete/rebuild > the dm-crypt block? You can overwrite the LUKS header multiple times and set up a new one. Btw: why do you want to overwrite the entire partition? In my eyes, this is some kind of rocket science and makes no sense, considering Kerckhoff's law.