From: Olaf Dietsche <olaf+list.linux-kernel@olafdietsche.de>
To: casey@schaufler-ca.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.6.25: access permission filesystem 0.21
Date: Tue, 13 May 2008 21:06:55 +0200 [thread overview]
Message-ID: <87k5hy2fcg.fsf@rat.lan> (raw)
In-Reply-To: 126313.89542.qm@web36605.mail.mud.yahoo.com
Casey Schaufler <casey@schaufler-ca.com> writes:
> --- Olaf Dietsche <olaf+list.linux-kernel@olafdietsche.de> wrote:
>
>> This patch adds a new permission managing file system.
>> Furthermore, it adds two modules, which make use of this file system.
>>
>> One module allows granting capabilities based on user-/groupid.
>
> Hmm. The primary purpose of the capability mechanism, according
> to the POSIX P1003.1e/2c working group*, is to separate the
> privilege mechanism from the userid mechanism. You are now
> reintegrating them two mechanims, albiet differently than
> they were integrated before. You can already achieve this end
> using filesystem based capabilties and mode bits and/or ACLs,
> so why the change?
This idea is from 2002, when there were neither filesystem based
capabilties nor ACLs. But since even I never used it, see it as an
interesting excercise.
>> The
>> second module allows to grant access to lower numbered ports based on
>> user-/groupid, too.
>
> Woof. As reasonable as mode bits on ports seems, there's an
> awful lot of tradition associated with the privileged port
> model. I can see the value in it, I've actually implemented
> it in the past in the Unix world, but I have never seen anyone
> willing to take advantage of the scheme.
Well, I'm not in the tradition business :-) but it's fun to do these
things and even useful in this case.
Regards, Olaf
next prev parent reply other threads:[~2008-05-13 19:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 20:59 [PATCH] 2.6.25: access permission filesystem 0.21 Olaf Dietsche
2008-05-12 22:06 ` Casey Schaufler
2008-05-13 19:06 ` Olaf Dietsche [this message]
2008-05-16 23:11 ` Randy Dunlap
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=87k5hy2fcg.fsf@rat.lan \
--to=olaf+list.linux-kernel@olafdietsche.de \
--cc=casey@schaufler-ca.com \
--cc=linux-kernel@vger.kernel.org \
/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