From: Hans Reiser <reiser@namesys.com>
To: Michael Halcrow <mike@halcrow.us>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Encrypted Filesystem
Date: Tue, 27 Jan 2004 13:51:30 -0800 [thread overview]
Message-ID: <4016DD62.7020905@namesys.com> (raw)
In-Reply-To: <20040127212546.GA10831@halcrow.us>
Michael Halcrow wrote:
>
> I am
>aware of reiser4; Hans may remember having lunch with me at the
>DISCEX-III conference in Washington, D.C. last year. My booth (the
>BYU Internet Security Research Lab; Trust Negotiation) was right
>across from his:
>
>http://csdl.computer.org/comp/proceedings/discex/2003/1897/02/1897toc.htm
>
>He had a lengthy discussion with Jason Holt[2] on the implementation
>of crypto in reiser4.
>
>While I appreciate the security features that are part of reiser4, my
>efforts toward filesystem encryption are aimed at a more general
>level, to provide an encryption layer that will work across several
>filesystems. Perhaps we can look into unifying and abstracting the
>key management, authentication, and other aspects involved in a
>comprehensive filesystem encryption system, extending and using kernel
>structures (struct file, kobject/sysfs, etc.) to maintain that data,
>so whether someone is using reiser4, Security Enhanced ext3 (SEext3),
>or Security Enhanced jfs (SEjfs)[3], the interface to userland will be
>the same.
>
>
I am in principle interested in doing this, especially since the area of
our inspiration is not in key management but in performance.
>
>[2] Hans: Jason was a co-worker of mine in the ISRL, skinny and tall
>with curly red hair (he's hard to forget once you've met him:
><http://isrl.cs.byu.edu/images/Dcp02290.jpg>)
>
>
Jason is working on a write only plugin (or at least he said so a few
months ago) for reiser4. You probably remember him discussing it then.
Where is your photo, or are you a CIA spy who needs to keep it
secret....;-) I remember three interesting people talked to me all at
once at that conference about reiser4 crypto and other things that crept
into that conversation, if you send your photo I can know if I remember
correctly which one other than Jason you were.
>[3] That was meant to be funny...
>.___________________________________________________________________.
> Michael A. Halcrow
> Security Software Engineer, IBM Linux Technology Center
>GnuPG Fingerprint: 05B5 08A8 713A 64C1 D35D 2371 2D3C FDDA 3EB6 601D
>
>
next prev parent reply other threads:[~2004-01-27 21:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16405.24299.945548.174085@laputa.namesys.com>
2004-01-26 19:02 ` Encrypted Filesystem Hans Reiser
2004-01-27 18:56 ` Edward Shishkin
2004-01-27 21:25 ` Michael Halcrow
2004-01-27 21:51 ` Hans Reiser [this message]
[not found] <OFA97B290B.67DE842E-ON87256E27.0061728C-86256E27.0061BB0E@us.ibm.com.suse.lists.linux.kernel>
2004-01-27 16:13 ` Andi Kleen
2004-01-27 18:17 ` Jari Ruusu
2004-01-27 18:44 ` Andi Kleen
2004-01-26 17:46 Michael A Halcrow
2004-01-26 19:06 ` Mark Borgerding
2004-01-26 21:04 ` Felipe Alfaro Solana
2004-01-30 17:01 ` Pavel Machek
2004-01-27 0:06 ` jw schultz
2004-01-27 0:43 ` Adam Sampson
2004-01-27 1:42 ` Andy Isaacson
2004-01-27 22:01 ` Jan Harkes
2004-01-27 22:16 ` Jean-Luc Cooke
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=4016DD62.7020905@namesys.com \
--to=reiser@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@halcrow.us \
/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