Linux filesystem development
 help / color / mirror / Atom feed
From: Chris Wright <chris@wirex.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	Trond Myklebust <trond.myklebust@fys.uio.no>,
	Linux FSdevel <linux-fsdevel@vger.kernel.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Dave McCracken <dmccr@us.ibm.com>
Subject: Re: [PATCH] Introduce BSD-style user credential [3/3]
Date: Fri, 30 Aug 2002 18:01:45 -0700	[thread overview]
Message-ID: <20020830180145.B11165@figure1.int.wirex.com> (raw)
In-Reply-To: <1030755064.1225.18.camel@irongate.swansea.linux.org.uk>; from alan@lxorguk.ukuu.org.uk on Sat, Aug 31, 2002 at 01:51:04AM +0100

* Alan Cox (alan@lxorguk.ukuu.org.uk) wrote:
> 
> Needs fsuid too, and space for the security LSM modules to attach
> private information. SELinux needs a few more credentials than base
> kernels!

Yes, I agree.  LSM is just using opaque blobs, so it's simple enough to
add.

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

  parent reply	other threads:[~2002-08-31  1:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <15727.64653.78081.277222@charged.uio.no>
2002-08-30 23:40 ` [PATCH] Introduce BSD-style user credential [3/3] Linus Torvalds
2002-08-31  0:24   ` Trond Myklebust
2002-08-31  0:49     ` Linus Torvalds
     [not found]     ` <Pine.LNX.4.44.0208301741430.5561-100000@home.transmeta.com>
2002-08-31  0:51       ` Alan Cox
2002-08-31  0:56         ` Trond Myklebust
2002-08-31  1:01         ` Chris Wright [this message]
2002-08-31  1:04         ` Linus Torvalds
2002-08-31 16:13         ` Daniel Phillips
2002-08-31 16:43           ` Alan Cox
2002-08-31  1:29       ` Trond Myklebust
2002-08-31  4:18         ` Linus Torvalds
2002-08-31 12:02           ` Kai Henningsen
2002-08-31 16:30           ` Trond Myklebust
2002-09-01 15:23             ` Daniel Phillips
2002-08-30 23:15 Trond Myklebust

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=20020830180145.B11165@figure1.int.wirex.com \
    --to=chris@wirex.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dmccr@us.ibm.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    --cc=trond.myklebust@fys.uio.no \
    /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