From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] SSDs & flash... and secure keyslot erase
Date: Fri, 24 Aug 2012 17:54:05 +0200 [thread overview]
Message-ID: <20120824155405.GC30694@tansi.org> (raw)
In-Reply-To: <50379C59.5020908@archlinux.org>
On Fri, Aug 24, 2012 at 05:23:05PM +0200, Thomas B?chler wrote:
> Am 24.08.2012 17:06, schrieb Milan Broz:
[...]
> > But there is no perfect solution.
>
> Interesting write-up. If you are really paranoid, it seems you must back
> up all data, perform ATA security erase and put the data back on the
> disk (and then perform ATA security erase on the backup).
That may not be enough, see Section 3.2 of
http://cseweb.ucsd.edu/users/swanson/papers/Fast2011SecErase.pdf
Unfortunately, no manufacturer names given.
My current take is that the only reliable thing is to have LUKS
key-slots individually larger than the spare area and then overwrite
all free space with random data after a key-slot change. That way
the SSD would be unable to hold an old key-slot. For a 240G
SSD that may mean key-slots > 16GB each. Also, you cannot be
sure how much Flash capacity an SSD actually has without
opening it.
Arno
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F
----
One of the painful things about our time is that those who feel certainty
are stupid, and those with any imagination and understanding are filled
with doubt and indecision. -- Bertrand Russell
next prev parent reply other threads:[~2012-08-24 15:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 15:06 [dm-crypt] SSDs & flash... and secure keyslot erase Milan Broz
2012-08-24 15:23 ` Thomas Bächler
2012-08-24 15:54 ` Arno Wagner [this message]
2012-08-24 15:59 ` Thomas Bächler
2012-08-24 15:46 ` Arno Wagner
2012-08-24 17:24 ` Christoph Anton Mitterer
2012-08-24 19:07 ` Milan Broz
2012-08-24 22:26 ` 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=20120824155405.GC30694@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.