encrypted filesystem

  • Valient Gough

    Valient Gough - 2002-12-20

    First let me say good job mali!

    I found lufs from an announcement a week or two ago and I've started playing with it to implement an encrypted filesystem.  I miss TCFS..

    A patch of my current work is available at http://www.pobox.com/~vgough/lufs  - the latest is changeset 1.10 as a diff from lufs 0.8.3 (lufs-0.8.3-encfs-1.10.patch.bz2).

    I haven't gotten to using decent encryption code yet, so it is using rot13 for the 'encryption' - convenient for testing that things are working, but obviously not secure (it doesn't even require a password to mount).  To use it, build and install it, then "lufsmount encfs:///tmp/crypt-real /tmp/crypt-fake"  , anything added to /tmp/crypt-fake is then stored as rot-13 in the /tmp/crypt-real directory, both filenames and file contents are processed..

    I've a couple questions though:  is it possible that a particular FileSystem instance will be asked to open a file more then once?  That is, will do_open be called in the same thread, for the same file multiple times before a do_release is called, or is that not possible due to the lufs layer?

    Second - I modified lufsmount to add "encfs" as one of the filesystem options.  Is that the right way to add a filesystem, or is it possible to add a filesystem without modifying lufs/util code?

    The other reason I'm writing is to see if anyone else is working on an encrypted filesystem based on lufs.  If you are, please post what you have, or ideas so we can discuss.

    Valient Gough

    • Florin Malita

      Florin Malita - 2003-01-25

      hi, sorry for being so terribly late...

      great to hear about an encrypted fs being developed ;)

      now, to answer your questions:

      yes, it is possible that do_open (xxxfs_open now) gets called multiple times in the same thread. there is no file state information held by lufs, it's all up to the fs implementation.

      (one of the reason for delaying my answer) it is possible now to pass arbitrary arguments to filesystems without lufsd/lufsmount knowledge of it. i've completely separated the filesystem modules from lufsd and lufsmount is no longer parsing fs specific options. so, filesystems can be even distributed separately from lufs now.

      i'm not aware of anyone besides you working on encripted filesystems for lufs.


Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks