linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: "Serge E. Hallyn" <hallyn@CS.WM.EDU>
Cc: liangbin01@iscas.cn, linux-kernel@vger.kernel.org,
	linux-security-module@wirex.com
Subject: Re: PROBLEM: A Capability LSM Module serious bug
Date: Mon, 8 Dec 2003 10:26:59 -0800	[thread overview]
Message-ID: <20031208102659.B10325@osdlab.pdx.osdl.net> (raw)
In-Reply-To: <20031208164854.GA15146@escher.cs.wm.edu>; from hallyn@CS.WM.EDU on Mon, Dec 08, 2003 at 11:48:54AM -0500

* Serge E. Hallyn (hallyn@CS.WM.EDU) wrote:
> The main question is do we declare cap_effective to belong solely to
> capability.c, or do we want capability.c to trust previous LSM's
> computations of those values?  So, even with the current case, if we
> insmod, rmmod, then re-insmod capability, do we want to revoke all
> previous cap_* computations?

This is a common issue with the opaque blobs as well.

> It seems reasonable for it "belong" to capability.c (and I've heard of
> noone else wanting to use it).  I just don't think we've explicitly
> declared this to be the case.

Unfortunately, it's currently used by kernel proper.  So we need a
generic solution.

thanks,
-chris
-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net

      reply	other threads:[~2003-12-08 18:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20031207121151.22328.qmail@abyss.iscas.cn>
     [not found] ` <20031208144028.GA13813@escher.cs.wm.edu>
     [not found]   ` <20031208161901.7964.qmail@abyss.iscas.cn>
2003-12-08 16:30     ` PROBLEM: A Capability LSM Module serious bug Serge E. Hallyn
     [not found] ` <20031208150809.GA14068@escher.cs.wm.edu>
     [not found]   ` <20031208163618.8789.qmail@abyss.iscas.cn>
2003-12-08 16:48     ` Serge E. Hallyn
2003-12-08 18:26       ` Chris Wright [this message]

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=20031208102659.B10325@osdlab.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=hallyn@CS.WM.EDU \
    --cc=liangbin01@iscas.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@wirex.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).