public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Casey Schaufler <casey@schaufler-ca.com>
To: "David P. Quigley" <dpquigl@tycho.nsa.gov>
Cc: Theodore Tso <tytso@mit.edu>, Markku Savela <msa@moth.iki.fi>,
	Pavel Machek <pavel@suse.cz>,
	linux-kernel@vger.kernel.org
Subject: Re: Frustrated with capabilities..
Date: Thu, 28 Aug 2008 21:47:15 -0700	[thread overview]
Message-ID: <48B77F53.6080200@schaufler-ca.com> (raw)
In-Reply-To: <1219957399.2627.127.camel@moss-terrapins.epoch.ncsc.mil>

David P. Quigley wrote:
> On Thu, 2008-08-28 at 13:48 -0400, Theodore Tso wrote:
>   
>> On Thu, Aug 28, 2008 at 05:45:34PM +0300, Markku Savela wrote:
>>     
>>>> From: Pavel Machek <pavel@suse.cz>
>>>>         
>>>> Yes, you need upcoming filesystem capabilities.  Binary may not
>>>> inherit capabilities unless filesystem flags permit that.
>>>>         
>>> I think this is wrong. Normal executables inherit uid/gid and
>>> supplementary groups by default. Why should capabilities be any
>>> different?
>>>       
>> Well, because that's not the what the POSIX draft specification (and
>> the rest of the Unix industry who were striving to meet the US
>> Department of Defense's "B2 by '92" initiative) ended up implementing.
>>     
>
> Minor nit. It was actually C2(Controlled Access Protection) by '92 which
> is mainly just DAC protections as opposed to B2(Structured Protection)
> which also included MAC policies and Sensitivity labels in addition to
> DAC protections

But the fun part was that the evaluation requirements for B1,
which fell in between C2 and B2 (the order from least secure to
most was D, C1, C2, B1, B2, B3, A1, and "Beyond A1") where so
close to those for C2 that everyone implemented B1, which did
include MAC policy in the form of Bell and LaPadula sensitivity.
The privilege model (now called capabilities, and you have to buy
me a beer to get the whole story) does not actually come in the
requirements until B3, although some people will argue that it
was intended they be included at B2. Even though no one even tried
a B3 and no one succeeded at B2 everyone did capabilities based
on one of the drafts or another.

Anyone who thinks that the capability scheme is wrong headed is
encouraged to read the P1003.1e/2c (withdrawn) DRAFT. It's on
the web in several places. You may end up still thinking it's
wrong, but at least you will have seen how the arguments got
hashed out.

And we're still not talking about the Jackson Hole meeting.



  reply	other threads:[~2008-08-29  4:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-27  9:31 Frustrated with capabilities Markku Savela
2008-08-28 14:18 ` Pavel Machek
2008-08-28 14:45   ` Markku Savela
2008-08-28 17:48     ` Theodore Tso
2008-08-28 21:03       ` David P. Quigley
2008-08-29  4:47         ` Casey Schaufler [this message]
2008-08-29 14:20           ` David P. Quigley
2008-08-29 10:18       ` Markku Savela
2008-08-29 10:47         ` James Morris
2008-08-29 14:07         ` Theodore Tso
2008-08-29 17:11         ` Serge E. Hallyn
2008-08-29 16:58   ` Serge E. Hallyn

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=48B77F53.6080200@schaufler-ca.com \
    --to=casey@schaufler-ca.com \
    --cc=dpquigl@tycho.nsa.gov \
    --cc=linux-kernel@vger.kernel.org \
    --cc=msa@moth.iki.fi \
    --cc=pavel@suse.cz \
    --cc=tytso@mit.edu \
    /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