From: Thomas Bastiani <thom@codehawks.eu>
To: Stephen Cousins <steve.cousins@maine.edu>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Is erasing hard disk drive mandatory?
Date: Fri, 30 May 2014 16:58:20 +0100 [thread overview]
Message-ID: <5388AA9C.3020909@codehawks.eu> (raw)
In-Reply-To: <CAMFqqRpk7b_1awwWOE_08JFLhtxRmzHDubz69ek96CHqRxQjCA@mail.gmail.com>
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
next prev parent reply other threads:[~2014-05-30 15:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 13:33 [dm-crypt] Is erasing hard disk drive mandatory? Kenny Lake
2014-05-29 20:13 ` Arno Wagner
2014-05-30 13:32 ` Stephen Cousins
2014-05-30 13:42 ` Arno Wagner
2014-05-30 13:52 ` Stephen Cousins
2014-05-30 15:07 ` Heinz Diehl
2014-05-30 15:17 ` Stephen Cousins
2014-05-30 15:58 ` Thomas Bastiani [this message]
2014-05-30 17:10 ` Heinz Diehl
2014-05-30 17:24 ` Thomas Bastiani
2014-05-30 17:47 ` Heinz Diehl
2014-05-30 17:57 ` Thomas Bastiani
2014-05-30 19:03 ` Laurence Darby
2014-05-30 19:25 ` Arno Wagner
2014-05-31 8:32 ` Heinz Diehl
2014-05-30 18:08 ` Arno Wagner
2014-05-30 10:02 ` Andrew
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=5388AA9C.3020909@codehawks.eu \
--to=thom@codehawks.eu \
--cc=dm-crypt@saout.de \
--cc=steve.cousins@maine.edu \
/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.