From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: Andrew Morton <akpm@digeo.com>, Chris Wright <chris@wirex.com>,
gj@pointblue.com.pl, Linus Torvalds <torvalds@transmeta.com>,
lkml <linux-kernel@vger.kernel.org>,
lsm <linux-security-module@wirex.com>,
Greg Kroah-Hartman <greg@kroah.com>
Subject: Re: [PATCH][LSM] Early init for security modules and various cleanups
Date: Mon, 02 Jun 2003 10:40:08 -0400 [thread overview]
Message-ID: <3EDB61C8.3020504@nortelnetworks.com> (raw)
In-Reply-To: 1054558223.1053.105.camel@moss-huskers.epoch.ncsc.mil
Stephen Smalley wrote:
> On Mon, 2003-06-02 at 06:44, Andrew Morton wrote:
>
>>Chris Wright <chris@wirex.com> wrote:
>>
>>>security_capable() returns 0 if that capability bit is set.
>>>
>>That's just bizarre. Is there any logic behind it?
>>
>
> The LSM access control hooks all return 0 on success (i.e. permission
> granted) and negative error code on failure, like most of the rest of
> the kernel interfaces (e.g. consider permission())
Maybe it should be called "security_incapable() and then the return code can be
treated as a boolean true/false....
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next prev parent reply other threads:[~2003-06-02 14:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-02 9:49 [BK PATCH][LSM] Early init for security modules and various cleanups Chris Wright
2003-06-02 9:54 ` [PATCH][LSM] " Chris Wright
2003-06-02 9:57 ` Chris Wright
2003-06-02 10:00 ` Chris Wright
2003-06-02 10:01 ` Chris Wright
2003-06-02 10:03 ` Chris Wright
2003-06-02 10:08 ` Grzegorz Jaskiewicz
2003-06-02 10:09 ` Chris Wright
2003-06-02 10:44 ` Andrew Morton
2003-06-02 12:50 ` Stephen Smalley
2003-06-02 14:40 ` Chris Friesen [this message]
2003-06-02 16:33 ` Chris Wright
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=3EDB61C8.3020504@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=akpm@digeo.com \
--cc=chris@wirex.com \
--cc=gj@pointblue.com.pl \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@wirex.com \
--cc=sds@epoch.ncsc.mil \
--cc=torvalds@transmeta.com \
/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.