public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Casey Schaufler <casey@schaufler-ca.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>,
	David Howells <dhowells@redhat.com>
Cc: viro@ftp.linux.org.uk, hch@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: Credentials test patch
Date: Tue, 18 Sep 2007 10:58:43 -0700 (PDT)	[thread overview]
Message-ID: <336243.38765.qm@web36610.mail.mud.yahoo.com> (raw)
In-Reply-To: <1190133857.6656.20.camel@heimdal.trondhjem.org>


--- Trond Myklebust <trond.myklebust@fys.uio.no> wrote:

> On Tue, 2007-09-18 at 17:33 +0100, David Howells wrote:
> > Hi Al, Christoph,
> > 
> > Here's a new version of my credentials patch.  It's still very basic, with
> > only Ext3, (V)FAT, NFS, AFS, SELinux and keyrings compiled in on an x86_64
> > arch kernel.  The patched kernel compiles, links and runs.
> > 
> > I've made the following major changes to the patch:
> > 
> >  (1) System calls that might want to use the credentials call
> >      update_current_cred() before calling into the VFS or whatever.  This
> >      allows the keyring pointers in the cred struct to be updated.
> > 
> >  (2) I've got rid of current_cred(), __current_cred() and the accessors for
> >      current's fsuid, fsgid and group list.  Instead you just use
> >      current->cred->whatever.  You don't need RCU to read the current
> threads
> >      credentials as only you are permitted to change them.
> > 
> > David
> > ---
> 
> What about the process' capabilities? Shouldn't they also be part of a
> credential?

As should the LSM security blob, if appropriate.

What I don't really understand is what value is gained by this exercise.
Are the savings sufficiently significant to justify the effort?


Casey Schaufler
casey@schaufler-ca.com

  parent reply	other threads:[~2007-09-18 17:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-13 19:56 Credentials test patch David Howells
2007-09-13 20:09 ` Linus Torvalds
2007-09-13 21:19   ` David Howells
2007-09-13 21:33     ` Linus Torvalds
2007-09-15 15:51 ` Ulrich Drepper
2007-09-17 11:02   ` David Howells
2007-09-17 14:28     ` Ulrich Drepper
2007-09-17 15:27 ` David Howells
2007-09-18 16:33 ` David Howells
2007-09-18 16:44   ` Trond Myklebust
2007-09-18 17:25     ` David Howells
2007-09-18 17:58     ` Casey Schaufler [this message]
2007-09-18 18:03       ` Trond Myklebust
2007-09-18 18:24         ` David Howells

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=336243.38765.qm@web36610.mail.mud.yahoo.com \
    --to=casey@schaufler-ca.com \
    --cc=dhowells@redhat.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    --cc=viro@ftp.linux.org.uk \
    /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