From: Hans Reiser <reiser@namesys.com>
To: Edward Shushkin <edward@namesys.com>
Cc: Valdis.Kletnieks@vt.edu, reiserfs-list@namesys.com,
reiserfs-dev@namesys.com
Subject: Re: Proposal for keying encrypted filesystem
Date: Fri, 04 Apr 2003 22:45:26 +0400 [thread overview]
Message-ID: <3E8DD2C6.2040106@namesys.com> (raw)
In-Reply-To: <3E8DBE93.8BAEAF29@namesys.com>
Edward Shushkin wrote:
>Hans Reiser wrote:
>
>
>>Edward Shushkin wrote:
>>
>>
>>
>>>Valdis.Kletnieks@vt.edu wrote:
>>>
>>>
>>>
>>>
>>>>On Fri, 04 Apr 2003 09:30:29 EST, Pierre Abbat <phma@webjockey.net> said:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>But I'd also like to be able to have several encrypted directories on one
>>>>>partition, with different keys, such that when I give the key any process
>>>>>with the right UID can access them. I might have a cron job that needs access
>>>>>
>>>>>
>>>>>to encrypted data.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>You need to apply "least privilege" - you don't give the key to any process
>>>>that doesn't need it. In your example, you would make sure that any process
>>>>running under UID nnn gets given the key, so that other processes couldn't
>>>>do anything even if they *did* access them.
>>>>
>>>>Properly applied, you can even leverage it further - for instance, if your
>>>>backup process doesn't have the key tokens, you can safely let it have access
>>>>to all the files - it can read the 127 meg of data to back it up in a bitwise
>>>>manner,
>>>>
>>>>
>>>>
>>>>
>>>I am sorry, bitwise manner seems to be impossible in reiser4: the only access
>>>to crypto files is via page cache, it requires a valid key..
>>>
>>>
>>>
>>this is not desirable.
>>
>>
>
>I understand, but direct io is incompatible with transaction semantics.
>
This means what?
> On the
>other hand, on the last seminar we made a conclusion to check key validness in
>oredr to avoid a possible security hole when read() first looks for uptodate
>(decrypted!) pages in memory before reading encrypted data from disk..
>
So how about making a key of 0 be a special case which gets you the file
in its encrypted form?
>
>
>
>>Encypted files need to be backed up too...
>>
>>
>
>They will be as ordinary unix files..
>
This means what?
>Edward.
>
>
>
>>>Edward.
>>>
>>>
>>>
>>>
>>>
>>>
>>>>but it can't actually DO anything with the data - this is something
>>>>that you can't do in the "give everything the token" model....
>>>>
>>>> ----------------------------------------------------------------------------------------------------
>>>> Part 1.2Type: application/pgp-signature
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>--
>>Hans
>>
>>
>
>
>
>
--
Hans
next prev parent reply other threads:[~2003-04-04 18:45 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-29 1:26 Proposal for keying encrypted filesystem Pierre Abbat
2003-03-29 16:46 ` Edward Shushkin
2003-03-29 16:55 ` Pierre Abbat
2003-03-29 18:17 ` Edward Shushkin
2003-03-29 20:49 ` Pierre Abbat
2003-03-30 10:12 ` Hendrik Visage
2003-03-30 17:00 ` Pierre Abbat
2003-03-31 9:15 ` Hendrik Visage
2003-03-30 16:30 ` Pierre Abbat
2003-03-31 11:21 ` Edward Shushkin
2003-03-31 12:09 ` Edward Shushkin
2003-03-31 13:36 ` Hendrik Visage
2003-03-31 13:54 ` Pierre Abbat
2003-03-31 16:35 ` Hendrik Visage
2003-03-31 20:11 ` Pierre Abbat
2003-03-31 21:31 ` Hendrik Visage
2003-03-31 22:40 ` Pierre Abbat
2003-04-01 9:31 ` Hendrik Visage
2003-03-31 13:58 ` Edward Shushkin
2003-03-31 16:45 ` Hendrik Visage
2003-04-01 12:28 ` Edward Shushkin
2003-04-01 16:06 ` Hans Reiser
2003-04-01 16:16 ` Anders Widman
2003-04-01 16:21 ` Hans Reiser
2003-04-02 2:56 ` Pierre Abbat
2003-04-02 6:06 ` Hans Reiser
2003-04-02 13:05 ` Pierre Abbat
2003-04-02 15:11 ` Edward Shushkin
2003-04-03 16:14 ` Valdis.Kletnieks
2003-04-03 19:43 ` Hans Reiser
2003-04-03 20:08 ` Valdis.Kletnieks
2003-04-03 19:44 ` Hans Reiser
2003-04-03 23:22 ` Pierre Abbat
2003-04-04 0:25 ` Russell Coker
2003-04-04 14:01 ` Valdis.Kletnieks
2003-04-04 14:30 ` Pierre Abbat
2003-04-04 14:47 ` Valdis.Kletnieks
2003-04-04 14:57 ` Pierre Abbat
2003-04-04 16:36 ` Edward Shushkin
2003-04-04 16:45 ` Valdis.Kletnieks
2003-04-04 15:25 ` Edward Shushkin
2003-04-04 16:50 ` Hans Reiser
2003-04-04 17:19 ` Edward Shushkin
2003-04-04 18:45 ` Hans Reiser [this message]
2003-04-05 0:01 ` Pierre Abbat
2003-04-07 0:44 ` Valdis.Kletnieks
2003-04-07 1:14 ` Pierre Abbat
2003-04-07 4:52 ` Valdis.Kletnieks
2003-04-07 16:55 ` Hans Reiser
2003-04-07 18:38 ` Edward Shushkin
2003-04-07 19:46 ` Hans Reiser
2003-04-07 22:36 ` Pierre Abbat
2003-04-08 10:10 ` Edward Shushkin
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=3E8DD2C6.2040106@namesys.com \
--to=reiser@namesys.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=edward@namesys.com \
--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.