From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Prepare SSD for encrypted linux install
Date: Thu, 9 Nov 2017 11:55:26 +0100 [thread overview]
Message-ID: <20171109105526.GA10687@tansi.org> (raw)
In-Reply-To: <ou07qm$61b$1@blaine.gmane.org>
On Thu, Nov 09, 2017 at 01:34:38 CET, Robert Nichols wrote:
> On 11/08/2017 11:36 AM, Merlin Büge wrote:
> >Hello all,
...
> >I thought of TRIMing the SSD via 'blkdiscard' instead of using
> >'ATA secure erase' after putting random data on it (twice, see [0]),
> >but that should make no difference, since the SSD will most probably
> >report all zeros for TRIMed sectors. Either way, the flash chips will
> >contain all random data ...
>
> No, they won't. They will all be cleared. The whole point of TRIM or
> blkdiscard is to allow the controller to clear the blocks of flash cells
> so that they will be immediately available for writing when needed.
> Writing random data to the flash cells and then immediately clearing them
> is fairly pointless. All it does is mask any residue a cleared cell might
> have of the last data it contained. People who need that level of
> security don't ask about it here.
And that is just it: To get any security benefit, the random
data must be still there on a read-back.
Hence the procedure is exactly the same as for a HDD:
Write random data to disk and leave it there, no "secure" erase,
no TRIM.
Regards,
Arno
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -- Plato
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
next prev parent reply other threads:[~2017-11-09 10:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 17:36 [dm-crypt] Prepare SSD for encrypted linux install Merlin Büge
2017-11-08 18:45 ` Heinz Diehl
2017-11-08 21:45 ` David Christensen
2017-11-09 0:34 ` Robert Nichols
2017-11-09 10:55 ` Arno Wagner [this message]
2017-11-09 11:05 ` Merlin Büge
2017-11-09 12:20 ` Arno Wagner
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=20171109105526.GA10687@tansi.org \
--to=arno@wagner.name \
--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 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.