From: "Alexander G. M. Smith" <agmsmith@rogers.com>
To: reiserfs-list@namesys.com
Subject: Re: Carrying Attributes too Far
Date: Tue, 23 Sep 2003 18:48:31 -0400 EDT [thread overview]
Message-ID: <1809297981-BeMail@cr593174-a> (raw)
In-Reply-To: <1064280061.3f6f9ffd2c514@webmail.st-andrews.ac.uk>
lrc1@st-andrews.ac.uk wrote on Tue, 23 Sep 2003 02:21:01 +0100:
> The question is whether the subfile metadata system will
> be compatible with permissions systems in which a user is able to revoke his
> own permissions to a file and then return them again - such as the current
> Unix permissions system - and what bodges you would accept to make it
> compatible.
That's a detail for deep thought, but I'll let someone else worry about it for now.
In my shallow thoughts, I'm leaning to having attributes identical to files, and permissions as a kind of attribute. The attribute's permission would be inherited from the file's permissions, if they don't have their own permission attributes (same inheritance rules for file permissions too).
A simple case would be to have only owners allowed to write, anyone to read (I said it was simple). Have an "owner" attribute. Only the matching user can write to a file marked with that attribute. Only the matching user can write to the file's contents, including data, attributes, which of course includes the owner attribute itself. Of course, this means the owner can give ownership of the file away to anyone he wants to (and contents if they don't have explicit permission attributes of their own).
That's just an example of a simple security scheme. A real one would be more sophisticated. And somebody else's problem :-)
- Alex
next prev parent reply other threads:[~2003-09-23 22:48 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-11 15:14 Fwd: Re: Reiser4: "pseudo file namespace" suggestion Narcoleptic Electron
2003-09-11 15:18 ` Hans Reiser
2003-09-13 23:59 ` Carrying Attributes too Far (was Reiser4: "pseudo file namespace" suggestion) Alexander G. M. Smith
2003-09-14 1:56 ` Mike Fedyk
2003-09-14 3:46 ` Alexander G. M. Smith
2003-09-14 3:53 ` Carrying Attributes too Far Hubert Chan
2003-09-14 4:21 ` Hubert Chan
2003-09-14 3:39 ` Hubert Chan
2003-09-14 4:21 ` Hubert Chan
2003-09-16 19:15 ` Alexander G. M. Smith
2003-09-18 17:14 ` Narcoleptic Electron
2003-09-18 18:08 ` Hans Reiser
2003-09-18 20:16 ` Alexander G. M. Smith
2003-09-18 20:31 ` Grant Miner
2003-09-18 21:44 ` Alexander G. M. Smith
2003-09-18 22:00 ` Grant Miner
2003-09-18 22:28 ` Narcoleptic Electron
2003-09-18 22:42 ` Hans Reiser
2003-09-18 23:06 ` Grant Miner
2003-09-18 23:17 ` Narcoleptic Electron
2003-09-18 23:23 ` Narcoleptic Electron
2003-09-18 23:28 ` Grant Miner
2003-09-19 0:29 ` Alexander G. M. Smith
2003-09-19 0:28 ` Alexander G. M. Smith
2003-09-19 0:46 ` Hans Reiser
2003-09-19 1:45 ` Narcoleptic Electron
2003-09-19 2:52 ` Alexander G. M. Smith
2003-09-19 4:40 ` Narcoleptic Electron
2003-09-19 8:42 ` Martin Wilck
2003-09-19 13:27 ` Alexander G. M. Smith
2003-09-19 15:13 ` Martin Wilck
2003-09-19 15:35 ` Alexander G. M. Smith
2003-09-19 15:48 ` Narcoleptic Electron
2003-09-19 13:20 ` Alexander G. M. Smith
2003-09-19 13:46 ` Bennett Todd
2003-09-19 19:31 ` Alexander G. M. Smith
2003-09-19 22:51 ` Narcoleptic Electron
2003-09-20 1:31 ` Hans Reiser
2003-09-22 15:53 ` Attribute Directory Name (Was: Carrying Attributes too Far) Narcoleptic Electron
2003-09-22 20:02 ` Narcoleptic Electron
2003-09-22 22:52 ` Alexander G. M. Smith
2003-09-22 13:28 ` Carrying Attributes too Far lrc1
2003-09-22 22:50 ` Alexander G. M. Smith
2003-09-23 1:21 ` lrc1
2003-09-23 22:48 ` Alexander G. M. Smith [this message]
2003-09-24 16:57 ` lrc1
2003-09-24 9:35 ` Hans Reiser
2003-09-24 17:52 ` lrc1
2003-09-24 19:37 ` Hubert Chan
2003-09-25 3:40 ` Hans Reiser
-- strict thread matches above, loose matches on Subject: below --
2003-10-04 5:58 lrc1
2003-10-04 18:17 ` Alexander G. M. Smith
2003-10-04 20:10 ` Hubert Chan
2003-12-03 19:18 ` Hans Reiser
2003-12-05 0:30 ` lrc1
2003-12-05 5:27 ` Hubert Chan
2003-12-05 12:38 ` Hans Reiser
2003-12-06 23:33 ` lrc1
2003-12-07 2:48 ` Hubert Chan
2003-12-07 17:08 ` 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=1809297981-BeMail@cr593174-a \
--to=agmsmith@rogers.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.