From: Andy Spencer <andy753421@gmail.com>
To: David Wagner <daw-news@cs.berkeley.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Privilege dropping security module
Date: Sat, 26 Sep 2009 21:09:58 +0000 [thread overview]
Message-ID: <20090926210958.GA23564@c.hsd1.tn.comcast.net> (raw)
In-Reply-To: <h9jaar$url$1@taverner.cs.berkeley.edu>
[-- Attachment #1: Type: text/plain, Size: 797 bytes --]
> As a result, in practice this interface to dpriv probably means that
> most implemented policies will be more permissive than
> intended/desired. I consider that a defect in the design of the
> specification language. It seems like it would be preferable to have
> a specification language that better facilitates secure use of dpriv.
What would you suggest as a better specification language? Would it be
sufficient to have recursive and non recursive variants for masking
permissions?
There's an implementation problem with using recursive permissions and
expanding * in userspace as well. If the user allows access to `foo' and
denies access to `foo/*', and later creates new entry of `foo/bar', the
new entry would have access allowed, which would probably not reflect
the users intent.
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-09-26 21:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 0:56 Andy Spencer
2009-09-23 20:46 ` Casey Schaufler
2009-09-23 22:31 ` Andy Spencer
2009-09-23 23:03 ` Tetsuo Handa
2009-09-24 16:37 ` David Wagner
2009-09-25 7:22 ` Andy Spencer
2009-09-25 20:48 ` David Wagner
2009-09-26 21:09 ` Andy Spencer [this message]
2009-09-27 0:28 ` David Wagner
2009-10-01 7:38 ` Pavel Machek
2009-10-01 9:15 ` Andy Spencer
2009-10-01 10:42 ` Pavel Machek
2009-09-23 21:31 ` [RFC][PATCH] " Andy Spencer
2009-09-24 16:25 ` Casey Schaufler
2009-09-25 10:06 ` Andy Spencer
2009-09-25 16:23 ` Casey Schaufler
2009-09-26 21:35 ` Andy Spencer
2009-09-28 5:38 ` Rob Meijer
2009-09-25 21:00 ` David Wagner
2009-09-29 7:36 ` Andy Spencer
2009-09-29 7:10 ` [RFC][PATCH] Permission masking security module (was dpriv) Andy Spencer
2009-09-29 17:44 ` Greg KH
2009-09-30 0:18 ` Andy Spencer
2009-10-01 2:33 ` Casey Schaufler
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=20090926210958.GA23564@c.hsd1.tn.comcast.net \
--to=andy753421@gmail.com \
--cc=daw-news@cs.berkeley.edu \
--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
all inboxes | Powered by JetHome®