All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Zidlicky <rz@linux-m68k.org>
To: Arno Wagner <arno@wagner.name>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] LUKS - SSD trim
Date: Sat, 24 Apr 2010 18:44:52 +0200	[thread overview]
Message-ID: <20100424164452.GA11910@linux-m68k.org> (raw)
In-Reply-To: <20100424155915.GC23598@tansi.org>

On Sat, Apr 24, 2010 at 05:59:15PM +0200, Arno Wagner wrote:
> On Sat, Apr 24, 2010 at 12:59:18AM +0200, Richard Zidlicky wrote:

> > it can be even much worse. The most evil case is a specially crafted device manufactured
> > by a mighty agency which will record every single read/write/trim command. A few weeks ago
> > it was on the news here that most copiers have builtin hard discs and make copies of what
> > people are copying.. so who knows what is in our ordinary hard discs today.
> 
> Only as temporary storage. Better copiers do a secure erase after
> the copy as well, but not all do. It is something copiers used
> for secret material can get certified for.

very offtopic, I would think there is certainly pressure from various agencies and companies
not to erase anything. Given that printers are programmed to print secret identification 
patterns on every page there could be quite a few surprises lurking in copiers.

> That is way you use encryoption on top. However, it is higly unlikely
> current HDDs/SSDs store a lot of information of this type. The storage
> space is just not there.

most will do clever traffic analysis trying to predict access patterns at the very least. 
Most likely not store everything to survive reboots but there can be exceptions.

Richard

  reply	other threads:[~2010-04-24 16:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-21 22:48 [dm-crypt] LUKS - SSD trim Felix Blanke
2010-04-21 23:00 ` Milan Broz
2010-04-21 23:03   ` Felix Blanke
2010-04-22  2:17     ` Arno Wagner
2010-04-22  8:42       ` mark
2010-04-22  9:37         ` Milan Broz
2010-04-22 20:12         ` Felix Blanke
2010-04-22 22:20           ` Richard Zidlicky
2010-04-22 22:22   ` Richard Zidlicky
2010-04-23  8:49     ` Milan Broz
2010-04-23 10:20       ` Mikko Rauhala
2010-04-23 11:13       ` Richard Zidlicky
2010-04-23 11:46         ` Milan Broz
2010-04-23 20:09           ` Richard Zidlicky
2010-04-23 20:45             ` Milan Broz
2010-04-23 22:59               ` Richard Zidlicky
2010-04-24 15:59                 ` Arno Wagner
2010-04-24 16:44                   ` Richard Zidlicky [this message]
2010-04-24 17:01                     ` Arno Wagner
2010-04-22  6:17 ` Heinz Diehl
2010-05-14  7:35 ` JG
  -- strict thread matches above, loose matches on Subject: below --
2010-05-27 13:14 Christoph Anton Mitterer

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=20100424164452.GA11910@linux-m68k.org \
    --to=rz@linux-m68k.org \
    --cc=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.