From: Hans Reiser <reiser@namesys.com>
To: Edward Shishkin <edward@namesys.com>
Cc: Reiserfs developers mail-list <Reiserfs-Dev@namesys.com>,
Reiserfs List <reiserfs-list@namesys.com>
Subject: Re: Basic interface for key management in reiser4 (DRAFT)
Date: Thu, 18 Aug 2005 17:30:58 -0700 [thread overview]
Message-ID: <43052842.6050505@namesys.com> (raw)
In-Reply-To: <4304D492.5010203@namesys.com>
Edward Shishkin wrote:
>>
>
>> What is a "plugin/regular"? Why
>> not "plugin/file"?
>>
>
> first, we have the following:
> #cat mydir/..../plugin/file
> 1 dir directory
>
> second, because the pseudo-file ..../plugin/file is readonly
you can change that, but perhaps better would be to cat "crypt_compress"
> mydir/..../children_inherit/plugin
> : it is impossible
> to change a file plugin of existing object in reiser4, whereas we want to
> have a pseudo-file to specify file plugins of children to create.
> Vitaly also suggested to rename "regular" to "creat" that sounds like
> creat (2)
>
>>
>>
>>
>>> #cat mydir/..../plugin/regular
>>> 1 cryptcompress Cryptcompress regular plugin
>>>
>>
>>
>> The above is cryptic to me.
>>
>>
>>
>>> #cat mydir/..../plugin/compression
>>> 0 lzo1 lzo1 compression transform
>>>
>>
>>
>> The above is cryptic to me.
>>
>
> 0 lzo1 lzo1 compression transform
>
> ^ ^ ^^^^^^^^^^^^^^^^^^^^^^^^^^
> | plugin label plugin description
> plugin id
Why not a separate file for each of these fields?
>
>
>> Is it a list of the allowed values for
>> compression algorithm? What is the 0?
>>
>>
>>
>>> #cat mydir/..../plugin/digest
>>> 1 sha256-32 sha256-32 digest transform
>>> #cat mydir/..../plugin/crypto
>>> 0 none absence of crypto transform
>>> #echo -e "blowfish\0" > mydir/..../plugin/crypto
>>>
>>> #touch mydir/myfile
>>> Unable to create file
>>> #cat mydir/..../keyload
>>> No key loaded
>>>
>>> #echo -e "08e19c2d91bbc14f06af9ec61e68\0" > mydir/..../keyload
>>> ^^----------------^^^^^^^^^^
>>> keysize key passphrase
>>>
>>> #cat mydir/..../keyload
>>> keyid32: f56ef868
>>> loaded 8-byte key for Blowfish cipher algo
>>>
>>> #echo "Hello World" > mydir/myfile
>>> #cd /
>>> #umount /mnt
>>> #mount /dev/hdb5 /mnt
>>> #cat /mnt/mydir/myfile
>>> Unable to open file
>>> #cat /mnt/mydir/myfile/..../keyload
>>> keyid32: f56ef868
>>> No key loaded
>>>
>>> #echo -e "08e19c2d91bbc14f06af9ec61e68\0" > /mnt/mydir/..../keyload
>>> #cat /mnt/mydir/myfile
>>> Hello World
>>>
>>
>>
>> When you load a key, who can access the file? Only the person who
>> loaded it, yes or?
>>
>
> Currently standard unix permissions work here.
but the idea is to use keys instead of standard unix permissions....
I think you need to store keys in a per process place, and allow
specifying whether children of a process inherit the keys somehow.
>
> Edward.
>
>
>
next prev parent reply other threads:[~2005-08-19 0:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-17 14:50 Basic interface for key management in reiser4 (DRAFT) Edward Shishkin
2005-08-17 19:52 ` Hans Reiser
2005-08-18 18:33 ` Edward Shishkin
2005-08-19 0:30 ` Hans Reiser [this message]
2005-08-19 4:18 ` Gregory Maxwell
2005-08-19 5:17 ` Hans Reiser
2005-08-19 7:16 ` Gregory Maxwell
2005-08-19 14:56 ` Edward Shishkin
2005-08-19 11:43 ` Edward Shishkin
2005-08-19 14:48 ` Gregory Maxwell
2005-08-19 10:45 ` Edward Shishkin
2005-08-23 15:48 ` Edward Shishkin
2005-08-24 0:52 ` Hans Reiser
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=43052842.6050505@namesys.com \
--to=reiser@namesys.com \
--cc=Reiserfs-Dev@namesys.com \
--cc=edward@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.