dm-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Joe Thornber <thornber@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: dm-crypt@saout.de
Subject: Re: [RFC] dm-thin: Random block placement strategy?
Date: Fri, 20 Jul 2012 09:50:59 +0000	[thread overview]
Message-ID: <20120720095058.GA1990@raspberrypi> (raw)
In-Reply-To: <ju9vdv$vpa$1@dough.gmane.org>

On Thu, Jul 19, 2012 at 02:49:51PM -0700, Alex Elsayed wrote:
> This may be insufficiently useful to justify implementing, but I thought it 
> was an interesting concept.
> 
> One of the current issues with dm-crypt and discard is that enabling it can 
> leak information about the filesystem and usage patterns of the disk[1].
> 
> If a dm-thin device with a random block placement strategy is layered on top 
> of dm-crypt however, this could solve some of the issues involved and 
> partially mitigate others.
> 
> Such a random block placement strategy would heavily disguise any layout 
> patterns that could be used to identify the filesystem, most likely to the 
> point of being completely unrecognizable.

A couple of things spring to mind.

- If you're using a spindle device this will destroy performance,
  unless you use large block size (which I suspect you don't want
  to do because you're trying to disguise access patterns).

- How expensive will acquiring a cryptographically secure random
  destination be?

      reply	other threads:[~2012-07-20  9:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-19 21:49 [RFC] dm-thin: Random block placement strategy? Alex Elsayed
2012-07-20  9:50 ` Joe Thornber [this message]

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=20120720095058.GA1990@raspberrypi \
    --to=thornber@redhat.com \
    --cc=dm-crypt@saout.de \
    --cc=dm-devel@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).