From: Eduard Bloch <edi@gmx.de>
To: "Mario 'BitKoenig' Holbe" <Mario.Holbe@TU-Ilmenau.DE>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Encrypting file system
Date: Mon, 6 Mar 2006 14:05:52 +0100 [thread overview]
Message-ID: <20060306130552.GA2121@debian> (raw)
In-Reply-To: <duh99h$i66$1@sea.gmane.org>
#include <hallo.h>
* Mario 'BitKoenig' Holbe [Mon, Mar 06 2006, 01:17:53PM]:
> V Bhanu Chandra <vbhanu.lkml@gmail.com> wrote:
> > I am thinking of designing and implementing a new native encrypting
> > file system for the linux kernel as a part of a student / research
> > project. Unlike dm-crypt/loop-AES/cryptoloop, I plan to target
> > slightly more ambitious user specifications such as: per-file random
> > secret encryption keys which are in-turn encrypted using the public
> > keys of all users having access to that filesystem object (a copy
> ...
> > Any comments / guidance / suggestions are most welcome and solicitated.
>
> Since you are talking about an encrypting filesystems but only
> referencing encrypting block devices... Have you had a look at encfs
> and/or StegFS already?
> At least one of the encrypting block devices you mentioned (I don't
> remember which one) already has the ability to have multiple keys.
IIRC encfs does something like this (global key protected with pass
phrase and optional per-file IVs). And there is a new development:
http://ecryptfs.sourceforge.net/
Eduard.
--
Fast jede Frau ist schön, wenn sie Charme hat. Fast jede Frau hat
Charme, wenn sie Scham hat.
-- Sigmund Graff
next prev parent reply other threads:[~2006-03-06 13:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-06 10:31 [RFC] Encrypting file system V Bhanu Chandra
2006-03-06 12:17 ` Mario 'BitKoenig' Holbe
2006-03-06 13:05 ` Eduard Bloch [this message]
2006-03-06 17:37 ` Michael Halcrow
2006-03-06 21:36 ` AMD64 X2 lost ticks on PM timer Timo Schroeter
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=20060306130552.GA2121@debian \
--to=edi@gmx.de \
--cc=Mario.Holbe@TU-Ilmenau.DE \
--cc=linux-kernel@vger.kernel.org \
/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.