From: Hans Reiser <reiser@namesys.com>
To: Pierre Abbat <phma@webjockey.net>
Cc: reiserfs-list@namesys.com, reiserfs-dev@namesys.com
Subject: Re: Reiser4 crypto-compression design
Date: Wed, 26 Mar 2003 21:33:51 +0300 [thread overview]
Message-ID: <3E81F28F.2050409@namesys.com> (raw)
In-Reply-To: <200303260730.34330.phma@webjockey.net>
Pierre Abbat wrote:
>On Tuesday 25 March 2003 14:52, Edward Shushkin wrote:
>
>
>> When user creates a crypto-file, the file system asks for a secret
>>key and calculates its id (128-bit word) which supposed to be stored
>>in file's stat-data on disk.
>> When user opens crypto-file, the file system asks for a secret key,
>>checks (by the id) if it is valid, and places a pointer to the
>>crypto-file info to the reiser4 specific part of inode. This info
>>includes cpu key words created by special method of the crypto plugin
>>by the valid secret key.
>>
>>
>
>Can a directory be marked as encrypted, so that all new files in the directory
>will be encrypted with the same key? Can a process hold an encryption key, so
>that all its children automatically can read files encrypted with that key?
>
>
>
>
>
Both of these are desirable features. We need to work out the details
of integrating with a PKI infrastructure.
--
Hans
next prev parent reply other threads:[~2003-03-26 18:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-25 19:52 Reiser4 crypto-compression design Edward Shushkin
2003-03-25 20:23 ` Hendrik Visage
2003-03-26 17:03 ` Edward Shushkin
2003-03-26 18:21 ` Hans Reiser
2003-03-26 18:53 ` Hendrik Visage
2003-03-27 16:15 ` Edward Shushkin
2003-03-26 12:30 ` Pierre Abbat
2003-03-26 18:33 ` Hans Reiser [this message]
2003-03-26 20:35 ` Hubert Chan
2003-03-26 21:39 ` Hans Reiser
2003-03-27 0:16 ` Pierre Abbat
2003-03-27 16:30 ` Hans Reiser
2003-03-27 23:34 ` Pierre Abbat
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=3E81F28F.2050409@namesys.com \
--to=reiser@namesys.com \
--cc=phma@webjockey.net \
--cc=reiserfs-dev@namesys.com \
--cc=reiserfs-list@namesys.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 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.