All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heinz Diehl <htd@fancy-poultry.org>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] simple ideas addressing ssd TRIM security concern
Date: Mon, 16 Apr 2012 21:53:32 +0200	[thread overview]
Message-ID: <20120416195332.GA2887@fancy-poultry.org> (raw)
In-Reply-To: <20120416024321.GB22656@tansi.org>

On 16.04.2012, Arno Wagner wrote: 

> > Weighing out really is the most difficult part when you have no tangible
> > data: how much is it difficult to break a TRIMed and crypted device?
 
> It is not difficult. It is impossible.

If this is true, then why not use it and end of story?

  reply	other threads:[~2012-04-16 19:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-14  1:23 [dm-crypt] simple ideas addressing ssd TRIM security concern alban bernard
2012-04-14  4:15 ` Arno Wagner
2012-04-14 22:22   ` alban bernard
2012-04-15  1:26     ` Arno Wagner
2012-04-15 14:55     ` Sven Eschenberg
2012-04-15 16:55       ` alban bernard
2012-04-15 22:48         ` Sven Eschenberg
2012-04-16  0:28           ` alban bernard
2012-04-16  2:43             ` Arno Wagner
2012-04-16 19:53               ` Heinz Diehl [this message]
2012-04-17  2:48                 ` 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=20120416195332.GA2887@fancy-poultry.org \
    --to=htd@fancy-poultry.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.