9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: jaketodd422@gmail.com (Jacob Todd)
Subject: [9fans] Encrypting file systems
Date: Wed, 30 Mar 2011 20:22:26 +0000	[thread overview]
Message-ID: <AANLkTi=o-Qtjo3Qc2Q4pHzCXyhTbwv1vmrA1LNVe7Jes@mail.gmail.com> (raw)
In-Reply-To: <86hbako79v.fsf@cmarib.ramside>

What i called cdfs was actually something for inferno, written in limbo.
It's on contrib, but I've already forgot where and what it's actual name
was. Cryptfs is either fs(3) or kfs(4) with block level encryption, i have
no idea which. It probably wasn't added because it wasn't 'critical' for
using the system.
On Mar 30, 2011 1:21 PM, <smiley at zenzebra.mv.com> wrote:
> Jacob Todd <jaketodd422 at gmail.com> writes:
>
>> There's two implementations that i know of: one is in russ' contrib, and
>> there another one called cbfs (i think), which is also on contrib,
although
>> i don't remember where. The latter version could be russ' implementation
>> with changes, it's been a while since I tried either. Russ' didn't
compile
>> at first, there were two variables with the same name iirc.
>
> I was able to find the former, but not the latter. Russ' "cryptfs"
> appears to be a modification of kfs. But isn't kfs one of the file
> systems that's now considered deprecated?
>
> How come crypto wasn't put right in fs(3)? It seems like doing that
> would give all disk-based file systems immediate cryptography support.
>
> Also, if you have any idea where I can find that "cbfs", please let me
> know...
>
> Thanks!
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.9fans.net/private/9fans/attachments/20110330/c536ad2e/attachment.html>


  parent reply	other threads:[~2011-03-30 20:22 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     ` Jacob Todd [this message]
2011-03-29 15:06 ` [9fans] Encrypting file systems ron minnich
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='AANLkTi=o-Qtjo3Qc2Q4pHzCXyhTbwv1vmrA1LNVe7Jes@mail.gmail.com' \
    --to=jaketodd422@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).