9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: rminnich@gmail.com (ron minnich)
Subject: [9fans] Encrypting file systems
Date: Tue, 29 Mar 2011 08:06:14 -0700	[thread overview]
Message-ID: <AANLkTimVg5TRmCNy31v_TVgh9L8QY8fdDjahPmyWJ=Gh@mail.gmail.com> (raw)
In-Reply-To: <86wrjivvi9.fsf@cmarib.ramside>

I've got a rejected-by-usenix paper somewhere about writing a 9p
encryption fs which you could stack on anything that served 9p:
exportfs, fossil, tarfs, whatever. It essentially attached to a 9p
server, you set the key, it encrypted/decrypted the data as it wrote
to its server.

The neat thing about such an encrypting server is you can stack it
anywhere you have  9p server, which is quite fun; you can even stack
it over another instance of itself. You don't need to be root to use
it. You can pick an arbitrary key and don't have to share it with
anyone. And so on.

I have no idea where it is at this point.

maybe you can take cfs and make encrypting?

ron



  parent reply	other threads:[~2011-03-29 15:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-29 14:42 smiley at zenzebra.mv.com
2011-03-29 14:54 ` Jacob Todd
2011-03-30 17:19   ` smiley at zenzebra.mv.com
2011-03-30 17:25     ` erik quanstrom
2011-03-31  0:12       ` smiley at zenzebra.mv.com
2011-03-31 11:02         ` Steve Simon
2011-03-31 11:55           ` erik quanstrom
2011-03-31 20:35           ` [9fans] kfs: i'm not dead yet! Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-05-12 10:03             ` Akshat Kumar
2011-03-30 17:42     ` [9fans] Problem installing Chris
2011-03-30 18:37       ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-03-30 20:25       ` Jacob Todd
2011-03-31  3:43         ` Chris
2011-03-31  3:51           ` Lyndon Nerenberg
2011-03-30 20:22     ` [9fans] Encrypting file systems Jacob Todd
2011-03-29 15:06 ` ron minnich [this message]
2011-03-30 20:47 ` Mechiel Lukkien
2011-03-29 23:24 [9fans] encrypting " erik quanstrom
2011-03-31 12:01 [9fans] Encrypting " erik quanstrom

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='AANLkTimVg5TRmCNy31v_TVgh9L8QY8fdDjahPmyWJ=Gh@mail.gmail.com' \
    --to=rminnich@gmail.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).