All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Bächler" <thomas@archlinux.org>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] SSDs & flash... and secure keyslot erase
Date: Fri, 24 Aug 2012 17:59:39 +0200	[thread overview]
Message-ID: <5037A4EB.2080201@archlinux.org> (raw)
In-Reply-To: <20120824155405.GC30694@tansi.org>

[-- Attachment #1: Type: text/plain, Size: 1104 bytes --]

Am 24.08.2012 17:54, schrieb Arno Wagner:
> 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. 

Okay then. If you are paranoid, burn the entire SSD if your passphrase
is corrupted.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]

  reply	other threads:[~2012-08-24 15:59 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
2012-08-24 15:59     ` Thomas Bächler [this message]
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=5037A4EB.2080201@archlinux.org \
    --to=thomas@archlinux.org \
    --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.