All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Joel Reardon <reardonj@inf.ethz.ch>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Security enhancement for UBIFS with secure erase feature
Date: Sun, 30 Oct 2011 14:51:36 +0200	[thread overview]
Message-ID: <1319979098.2126.45.camel@koala> (raw)
In-Reply-To: <loom.20111027T111843-772@post.gmane.org>

Hi Joel,

On Thu, 2011-10-27 at 09:33 +0000, Joel Reardon wrote:
> So coincidentally I've been working on a secure deletion patch for UBIFS. (I'm a
> grad student researching secure deletion here in Zurich.) I'm mostly finished
> implementing it and the results are really good. It works by encrypting each
> data node individually with a different key, storing the keys in a (logically)
> fixed area, and then periodically atomically updating the key blocks to purge
> the old
> unwanted keys.

Sounds like a clever solution! It is curious to see how you made sure
that all this is power-cut safe.

> I have a couple questions to ask the main developer, mostly about orphans for
> which I found the documentation not quite clear. I'm quite keen to get
> this integrated into UBIFS, however this will be the first time I've
> contributed to the kernel so in this regard I'm unsure of the best practices
> and so forth.

Well, ask questions, send patches. This sounds very interesting.
However, I do not know if anyone will use this, hopefully yes!

Artem.

  reply	other threads:[~2011-10-30 12:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-08 14:35 Security enhancement for UBIFS with secure erase feature Stelling Carsten
2011-09-11 13:22 ` Artem Bityutskiy
2011-10-27  9:33   ` Joel Reardon
2011-10-30 12:51     ` Artem Bityutskiy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-10-31 17:51 Stelling Carsten
2011-09-05 16:01 Stelling Carsten
2011-09-08 11:18 ` Atlant Schmidt

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=1319979098.2126.45.camel@koala \
    --to=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=reardonj@inf.ethz.ch \
    /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.