From: Casey Schaufler <casey@schaufler-ca.com>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
casey@schaufler-ca.com
Cc: crispin@crispincowan.com, simon@fire.lp0.eu,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, cliffe@ii.net,
oiaohm@gmail.com
Subject: Re: Defense in depth: LSM *modules*, not a static interface
Date: Tue, 6 Nov 2007 20:34:45 -0800 (PST) [thread overview]
Message-ID: <538323.91702.qm@web36614.mail.mud.yahoo.com> (raw)
In-Reply-To: <200711070411.lA74Bdvn041341@www262.sakura.ne.jp>
--- Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp> wrote:
> Hello.
>
> Casey Schaufler wrote:
> > Fine grained capabilities are a bonus, and there are lots of
> > people who think that it would be really nifty if there were a
> > separate capability for each "if" in the kernel. I personally
> > don't see need for more than about 20. That is a matter of taste.
> > DG/UX ended up with 330 and I say that's too many.
>
> TOMOYO Linux has own (non-POSIX) capability that can support 65536
> capabilities
> if there *were* a separate capability for each "if" in the kernel.
>
http://svn.sourceforge.jp/cgi-bin/viewcvs.cgi/trunk/2.1.x/tomoyo-lsm/patches/tomoyo-capability.diff?root=tomoyo&view=markup
>
> The reason I don't use POSIX capability is that the maximum types are limited
> to
> bitwidth of a variable (i.e. currently 32, or are we going to extend it to
> 64).
> This leads to abuse of CAP_SYS_ADMIN capability.
That is a matter of taste.
> In other words, it makes fine-grained privilege division impossible.
I personally believe that a finer granularity than about 20
is too fine. I understand that this is a minority opinion.
Casey Schaufler
casey@schaufler-ca.com
next prev parent reply other threads:[~2007-11-07 4:35 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 19:04 Linux Security *Module* Framework (Was: LSM conversion to static interface) Rob Meijer
2007-10-29 19:41 ` Crispin Cowan
2007-10-30 5:13 ` Peter Dolding
2007-10-30 7:14 ` Defense in depth: LSM *modules*, not a static interface Cliffe
2007-10-30 6:55 ` Al Viro
2007-10-30 7:55 ` Crispin Cowan
2007-10-30 15:01 ` Casey Schaufler
2007-10-30 8:00 ` Cliffe
2007-10-30 12:30 ` Simon Arlott
2007-11-06 3:46 ` Crispin Cowan
2007-11-06 7:26 ` Cliffe
2007-11-06 23:59 ` Peter Dolding
2007-11-07 3:50 ` Cliffe
2007-11-07 3:35 ` Casey Schaufler
2007-11-07 4:11 ` Tetsuo Handa
2007-11-07 4:34 ` Peter Dolding
2007-11-07 4:34 ` Casey Schaufler [this message]
2007-10-30 18:42 ` Linux Security *Module* Framework (Was: LSM conversion to static interface) Jan Engelhardt
2007-10-30 19:14 ` Casey Schaufler
2007-10-30 19:50 ` Jan Engelhardt
2007-10-30 23:38 ` Peter Dolding
2007-10-31 0:16 ` david
2007-10-31 2:21 ` Peter Dolding
2007-10-31 3:43 ` Casey Schaufler
2007-10-31 5:08 ` david
2007-10-31 6:43 ` Crispin Cowan
2007-10-31 9:03 ` Peter Dolding
2007-10-31 10:10 ` Toshiharu Harada
2007-11-01 2:04 ` Peter Dolding
2007-11-01 2:20 ` Casey Schaufler
2007-11-01 2:51 ` Peter Dolding
2007-11-01 7:17 ` Jan Engelhardt
2007-11-01 11:49 ` David Newall
2007-11-04 1:28 ` Peter Dolding
2007-11-05 6:56 ` Andrew Morgan
2007-11-05 13:29 ` Serge E. Hallyn
2007-10-29 20:27 ` 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=538323.91702.qm@web36614.mail.mud.yahoo.com \
--to=casey@schaufler-ca.com \
--cc=cliffe@ii.net \
--cc=crispin@crispincowan.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=oiaohm@gmail.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=simon@fire.lp0.eu \
/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.