public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: Chris Wright <chrisw@osdl.org>
Cc: Stephen Smalley <sds@epoch.ncsc.mil>, Greg Kroah <greg@kroah.com>,
	Kurt Garloff <garloff@suse.de>,
	linux-security-module@wirex.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] Remove unnecesary capability hooks in rootplug.
Date: Thu, 25 Aug 2005 14:13:50 -0700	[thread overview]
Message-ID: <20050825211350.GA7762@shell0.pdx.osdl.net> (raw)
In-Reply-To: <20050825170617.GW7762@shell0.pdx.osdl.net>

* Chris Wright (chrisw@osdl.org) wrote:
> * Stephen Smalley (sds@epoch.ncsc.mil) wrote:
> > e.g. if secondary_ops->capable is null, the SELinux tests aren't going
> > to show that, because they will still see that the SELinux permission
> > checks are working correctly.  They only test failure/success for the
> > SELinux permission checks, not for the capability checks, so if you
> > unhook capabilities, they won't notice.
> 
> Yes, I see.  I thought the tests you were referring to were 
> "if (secondary_ops->capable)" not LTP tests.  Capability is still a
> module that can be loaded (or built-in).  So the only issue is it's
> security_ops is now NULL where it was a trivial return 0 function.
> Aside from the oversight Serge fixed, I don't think there's any issue.

Bah, of course, that's inaccurate because you unconditionally set the
secondary to the default.  So, indeed, the default case (nothing actively
loaded as secondary) will get secondary_ops filled with NULL only.
Seems simplest to just fill the default with cap calls where applicable,
but I had hoped to eliminate that.
Thoughts?

thanks,
-chris

  reply	other threads:[~2005-08-25 21:13 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-25  1:20 [PATCH 0/5] LSM hook updates Chris Wright
2005-08-25  1:20 ` [PATCH 1/5] Use capabilities as default w/ and w/out CONFIG_SECURITY Chris Wright
2005-08-25  1:20 ` [PATCH 2/5] Rework stubs in security.h Chris Wright
2005-08-26 17:31   ` Tony Jones
2005-08-26 17:59     ` Chris Wright
2005-08-26 18:03       ` Tony Jones
2005-08-26 18:00     ` Stephen Smalley
2005-08-26 18:08       ` Chris Wright
2005-08-26 18:11       ` Tony Jones
2005-08-25  1:20 ` [PATCH 3/5] Call security hooks conditionally if the security_op is filled out Chris Wright
2005-08-25  8:50   ` Kurt Garloff
2005-08-25 16:24     ` Chris Wright
2005-08-25  1:20 ` [PATCH 4/5] Remove unnecessary default capability callbacks Chris Wright
2005-08-25  1:20 ` [PATCH 5/5] Remove unnecesary capability hooks in rootplug Chris Wright
2005-08-25 14:38   ` serue
2005-08-25 15:13     ` Stephen Smalley
2005-08-25 16:21       ` Chris Wright
2005-08-25 16:23         ` Stephen Smalley
2005-08-25 17:06           ` Chris Wright
2005-08-25 21:13             ` Chris Wright [this message]
2005-08-25 16:28         ` serue
2005-08-25 21:12     ` Chris Wright
2005-08-31  6:34   ` Greg KH
2005-08-31 15:09     ` Chris Wright
2005-08-25  4:39 ` [PATCH 0/5] LSM hook updates James Morris
2005-08-25  5:32   ` Chris Wright
2005-08-25 19:15     ` Chris Wright
2005-08-26  9:23       ` serue
2005-08-26 13:27         ` Stephen Smalley
2005-08-26 10:30           ` serue
2005-08-26 16:41         ` Chris Wright
2005-08-26 17:35           ` serue
2005-08-26 17:49             ` Chris Wright
2005-08-25  9:52 ` serue
2005-08-25 10:18   ` serue
2005-08-25 16:19     ` 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=20050825211350.GA7762@shell0.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=garloff@suse.de \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@wirex.com \
    --cc=sds@epoch.ncsc.mil \
    /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