From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wg0-f41.google.com (mail-wg0-f41.google.com [74.125.82.41]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Fri, 30 May 2014 17:58:23 +0200 (CEST) Received: by mail-wg0-f41.google.com with SMTP id z12so2226635wgg.24 for ; Fri, 30 May 2014 08:58:22 -0700 (PDT) Message-ID: <5388AA9C.3020909@codehawks.eu> Date: Fri, 30 May 2014 16:58:20 +0100 From: Thomas Bastiani MIME-Version: 1.0 References: <1401370403.94216.YahooMailNeo@web172002.mail.ir2.yahoo.com> <20140529201335.GA9014@tansi.org> <20140530134238.GA21698@tansi.org> <20140530150701.GA4281@fancy-poultry.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] Is erasing hard disk drive mandatory? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stephen Cousins Cc: dm-crypt@saout.de On 05/30/14 16:17, Stephen Cousins wrote: > Hi Heinz, > > I agree. The field, by it's very nature, has varying levels of paranoia > (rightly so as we are seeing these days) and this level is more than what I > need for my purposes so I can save some time by not having to send random > data to all of the drives during the build process. > > Steve > I tend to do the erase pass because it doesn't have a performance cost on hard drives. On SSD's though, this would prevent TRIM from functioning properly and make the SSD appear as full to the controller which would hurt performance. So I tend to not erase SSDs with random data before encryption. The other thing is if you TRIM NAND cells on your SSD their contents should be unrecoverable as opposed to standard hard-drives. -- Thomas