From: Andrew Morton <akpm@linux-foundation.org>
To: casey@schaufler-ca.com
Cc: torvalds@linux-foundation.org, morgan@kernel.org,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH] -mm (2.4.26-rc3-mm1) v2 Smack using capabilities 32 and 33
Date: Tue, 27 Nov 2007 13:16:32 -0800 [thread overview]
Message-ID: <20071127131632.808bf9f8.akpm@linux-foundation.org> (raw)
In-Reply-To: <474B2EE0.5080102@schaufler-ca.com>
On Mon, 26 Nov 2007 12:38:56 -0800
Casey Schaufler <casey@schaufler-ca.com> wrote:
> From: Casey Schaufler <casey@schaufler-ca.com>
>
> This patch takes advantage of the increase in capability bits
> to allocate capabilities for Mandatory Access Control. Whereas
> Smack was overloading a previously allocated capability it is
> now using a pair, one for overriding access control checks and
> the other for changes to the MAC configuration.
>
> The two capabilities allocated should be obvious in their intent.
> The comments in capability.h are intended to make it clear that
> there is no intention that implementations of MAC LSM modules
> be any more constrained by the presence of these capabilities
> than an implementation of DAC LSM modules are by the analogous
> DAC capabilities.
>
>
> + !__capable(current, CAP_MAC_ADMIN))
> + !__capable(current, CAP_MAC_ADMIN))
Is there any reason for not using plain old capable() here?
next prev parent reply other threads:[~2007-11-27 21:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 20:38 [PATCH] -mm (2.4.26-rc3-mm1) v2 Smack using capabilities 32 and 33 Casey Schaufler
2007-11-26 21:36 ` Serge E. Hallyn
2007-11-27 3:22 ` Andrew Morgan
2007-11-27 21:16 ` Andrew Morton [this message]
2007-11-27 21:48 ` 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=20071127131632.808bf9f8.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=casey@schaufler-ca.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=morgan@kernel.org \
--cc=torvalds@linux-foundation.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 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.