DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Encrypted partitions with sectors to zero?
Date: Thu, 24 Oct 2013 13:53:57 +0200	[thread overview]
Message-ID: <20131024115357.GA7728@tansi.org> (raw)
In-Reply-To: <CAO1iXZ+-ZVK-bZKX4Kn9_MjKkebG7W1n4+eiViK1CTvaz1+qTg@mail.gmail.com>

On Thu, Oct 24, 2013 at 09:33:47AM +0200, Thomas Martin wrote:
> Hello Arno.
> 
> > Encryption does not overwrite your data. If you want that
> > with LUKS or plain dm-crypt, ypu need to do the overwrite
> > yyourself. Some tools, like TrueCrypt, offer you to do
> > this optionally during installation.
> >
> > See also FAQ item 5.3.
> 
> My bad, this is actually obvious (I always used shred when I was
> converting my old unsecured machines before encrypting them).
> 
> 
> > Yes. See FAQ item 5.3. If you do it for an already created
> > filesystem, you will not reach everything though, that is
> > why the overwrite should be done after crypto-mapping, but
> > before filesystem creation.
> >
> > Arno
> 
> Good point, I was looking to avoid insecurities by disabling TRIM but
> I didn't understood that this insecurity was "by default" even
> wwithout TRIM (as I didn't filled the LUKS container).
> 
> 
> Thanks a lot Arno, this is a lot more understandable for me now.

You are welcome. SSDs are still a security risk with regard
to some features, namely erasing old data, changing
passphrases and securely erasing a LUKS container, see FAQ 
Item 5.19. If you understand these issues and accept the associated
risks, encryption on SSDs is still a lot more secure than no 
encryption.

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
----
There are two ways of constructing a software design: One way is to make it
so simple that there are obviously no deficiencies, and the other way is to
make it so complicated that there are no obvious deficiencies. The first
method is far more difficult.  --Tony Hoare

  reply	other threads:[~2013-10-24 11:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-24  7:33 [dm-crypt] Encrypted partitions with sectors to zero? Thomas Martin
2013-10-24 11:53 ` Arno Wagner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-10-23 14:24 Thomas Martin
2013-10-23 18:04 ` 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=20131024115357.GA7728@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox