From: Matthias Schniedermeyer <ms@citd.de>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] SSD disks and cryptsetup-reencrypt
Date: Thu, 13 Jun 2013 01:43:22 +0200 [thread overview]
Message-ID: <20130612234322.GA21746@citd.de> (raw)
In-Reply-To: <20130612223021.GC14932@tansi.org>
On 13.06.2013 00:30, Arno Wagner wrote:
>
> That said, unless you have high-resource attackers to defend
> against, with something like, say, 8 complete-disk re-encryptions
> you should be relatively secure. But don't blame me if it turns
> out you are not.
Or use one of the newer SSDs that take "the easy way" for secure
erasing.
At last one or more of the current generation controller chips encrypt
the contents by default (even without enabling FDE), as the controller
has to do some form of scrambling anyway as high-entrophy is better for
the flash cells(*). So at least one does AES256 encryption always. When
you secure erase such a SSD they typically just generate a new key and
not actually erase the flash-cells. The unknown is if they "drop" the
old key in a secure way, but if they do there is no way to decrypt older
content even if you desolder the flash-chips.
Also you have to have to hope that key generation is really random. That
is something that can't really be proven (only disproven), so personally
that is not something i could rely on. So i classify it as a "nice to
have", if it works it is a line of defense otherwise it is "nothing".
Problem is i can't remember which one(s) do(es) that, and it's bed time.
:-)
*:
Something about preventing long streams of zeros, ones or both.
--
Matthias
next prev parent reply other threads:[~2013-06-12 23:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 14:44 [dm-crypt] SSD disks and cryptsetup-reencrypt octane indice
2013-06-12 22:30 ` Arno Wagner
2013-06-12 23:43 ` Matthias Schniedermeyer [this message]
2013-06-13 5:51 ` Yves-Alexis Perez
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=20130612234322.GA21746@citd.de \
--to=ms@citd.de \
--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.