Date: Fri, 20 Jun 2003 12:57:25 -0400 From: Erez Zadok <ezk@cs.sunysb.edu> To: Michael Sierchio <kudzu@tenebras.com> Cc: fs@freebsd.org Subject: Re: ideas about a unioning file system Message-ID: <200306201657.h5KGvPDs007736@agora.fsl.cs.sunysb.edu> In-Reply-To: Your message of "Fri, 20 Jun 2003 07:32:37 PDT." <3EF31B05.5070004@tenebras.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <3EF31B05.5070004@tenebras.com>, Michael Sierchio writes: > Poul-Henning Kamp wrote: > > > The majority of the problems we have in this area can be nailed down > > to only two issues: > > 1. The very tricky semantics of rename(2) > > 2. read/write/mmap coherency for stacked filesystems. > > This is of particular interest to me. While Poul-Henning has > done some very interesting work on encryption at the GEOM > level, I'm trying to work with ACL filesystems and stacking > crypto filesystems that manage keys with one per file. Yup, coherency is certainly a difficult problem. We have only begun to look at it, and implemented some simple solutions (for NCryptfs). We'll be exploring something more like Heidemann's work (SOSP'95) in the future. > Imagine the coherency problems when pages don't match up > because of IVs for CBC block mode encryption, and imagine > the headache for (un-)locking pages at different levels. Those of you doing crypto f/s, might be interested in reading our paper on NCryptfs, which was just presented at Usenix: http://www.fsl.cs.sunysb.edu/papers/ > Making it easy for FIST and cryptfs (Erez Zadok's stuff) would > be very helpful. (I.e. gee, I'd rather not have to do this > on Linux). BTW, we've completed a port of the fist templates to 4.x (all versions) and 5.0. We're planning to release a new fistgen RSN. Erez.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200306201657.h5KGvPDs007736>