mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: David Howells <dhowells@redhat.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
	Blair Strang <bls@asterisk.co.nz>,
	Kyle Moffett <mrmacman_g4@mac.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: In-kernel Authentication Tokens (PAGs)
Date: Tue, 15 Jun 2004 15:29:12 -0700	[thread overview]
Message-ID: <20040615152912.C22989@build.pdx.osdl.net> (raw)
In-Reply-To: <8666.1087292194@redhat.com>; from dhowells@redhat.com on Tue, Jun 15, 2004 at 10:36:34AM +0100

* David Howells (dhowells@redhat.com) wrote:
> You might want to look at this patch. It's what I've come up with to support
> kafs, but it's general, and should work for anything. It's been built along
> Linus's guidelines, and has Linus's approval, contingent on something actually
> using it fully.
> 
> You can use the session keyring number as a PAG ID if you wish.
> 
> I've a sample aklog program (key submission) should you be interested.

I'd be intereseted.  BTW, I just took a brief look and had a quick
question.

> +	if (bprm->e_uid != current->uid)
> +		suid_keys(current);
> +	exec_keys(current);
> +

would the security module be expected update/revoke keys if the thing changes
security domains on exec?

>  	task_lock(current);
>  	unsafe = unsafe_exec(current);
>  	security_bprm_apply_creds(bprm, unsafe);

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

  parent reply	other threads:[~2004-06-15 22:29 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-12  2:37 Kyle Moffett
2004-06-12  3:13 ` Andy Lutomirski
2004-06-12  4:57   ` Kyle Moffett
2004-06-12  5:34     ` Andy Lutomirski
2004-06-12 12:51       ` Kyle Moffett
2004-06-12 15:37         ` Andy Lutomirski
2004-06-12 17:15           ` Kyle Moffett
2004-06-12  3:15 ` Chris Wright
2004-06-12  4:48   ` Kyle Moffett
2004-06-12 20:53     ` Chris Wright
2004-06-12 21:15       ` Kyle Moffett
2004-06-12 21:44         ` Chris Wright
2004-06-12 21:58           ` Kyle Moffett
2004-06-12 22:51             ` Chris Wright
2004-06-12 23:40               ` Kyle Moffett
2004-06-12 22:51 ` Trond Myklebust
2004-06-12 23:33   ` Kyle Moffett
2004-06-12 23:58     ` Trond Myklebust
2004-06-13  0:23       ` Kyle Moffett
2004-06-15  6:38         ` Blair Strang
2004-06-15  7:03           ` Trond Myklebust
2004-06-15  9:36           ` David Howells
2004-06-15 19:00             ` Kyle Moffett
2004-06-15 22:07               ` Chris Wright
2004-06-15 23:48                 ` Kyle Moffett
2004-06-16  0:01                   ` Chris Wright
2004-06-16  0:06                     ` Kyle Moffett
2004-06-15 22:29             ` Chris Wright [this message]
2004-06-15 23:59             ` Kyle Moffett
2004-06-16 14:22             ` David Howells
2004-06-16 14:37             ` David Howells
2004-06-16 14:49             ` David Howells
2004-06-17  1:13               ` Kyle Moffett
2004-06-17 11:48               ` David Howells
2004-06-17 19:06                 ` Kyle Moffett
2004-06-23 12:29                 ` David Howells
2004-06-23 21:03                   ` Kyle Moffett
2004-06-29 17:07                   ` Kyle Moffett
2004-07-07 18:54                     ` John Bucy
2004-07-08  1:29                       ` Kyle Moffett

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=20040615152912.C22989@build.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=bls@asterisk.co.nz \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mrmacman_g4@mac.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

Powered by JetHome