public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@warthog.cambridge.redhat.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: David Howells <dhowells@redhat.com>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	openafs-devel@openafs.org
Subject: Re: [PATCH] in-core AFS multiplexor and PAG support
Date: Tue, 13 May 2003 17:05:57 +0100	[thread overview]
Message-ID: <8812.1052841957@warthog.warthog> (raw)
In-Reply-To: <Pine.LNX.4.44.0305130849480.1562-100000@home.transmeta.com>


Linus Torvalds wrote:
> On Tue, 13 May 2003, David Howells wrote:
> > 
> >  (1) PAG (Process Authentication Group) support. A PAG is ID'd by a unique
> >      number, and is represented in memory as a structure that has a ring of
> >      associated authentication tokens.
> > 
> >      Each process can either be part of a PAG, or it can PAG-less - in
> >      which case it has no authentication tokens.
> > 
> >      Two new syscalls are added: setpag and getpag.
> 
> I think the code looks pretty horrible,

Any particular bits?

> but I think we'll need something like this to keep track of keys. However,
> I'm not sure we should make this a new structure - I think we should make
> the current "tsk->user" thing _be_ the "PAG".

Maybe... There are arguments either way, but if the token ring is kept in
struct user, a task can't detach from it and pass a token-less set of keys
onto another process it wants to run.

Also, using a separate PAG structure means that you can lend your keys to an
SUID program and conversely it means a SUID program can't so easily gain
access to keys it didn't inherit from its caller.

I'm not sure that the ability to arbitrarily join a PAG should be permitted,
but it was requested.

David

  parent reply	other threads:[~2003-05-13 16:05 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-13 15:39 [PATCH] in-core AFS multiplexor and PAG support David Howells
2003-05-13 15:52 ` Linus Torvalds
2003-05-13 15:44   ` Alan Cox
2003-05-13 16:52     ` Jan Harkes
2003-05-13 16:57     ` Linus Torvalds
2003-05-13 16:39       ` Alan Cox
2003-05-13 21:46     ` Russ Allbery
2003-05-16 15:38     ` [OpenAFS-devel] " Derek Atkins
2003-05-13 16:05   ` David Howells [this message]
2003-05-13 16:24     ` Douglas E. Engert
2003-05-13 16:47     ` Linus Torvalds
2003-05-13 17:20       ` Jan Harkes
2003-05-13 18:21         ` David Howells
2003-05-13 18:51         ` Douglas E. Engert
2003-05-13 20:33           ` [OpenAFS-devel] " Jan Harkes
2003-05-13 21:26             ` Douglas E. Engert
2003-05-13 21:40               ` [OpenAFS-devel] " Jan Harkes
2003-05-13 22:14                 ` Douglas E. Engert
2003-05-14  2:02                   ` Jan Harkes
2003-05-17 12:30         ` Pavel Machek
2003-05-18 14:22           ` Nathan Neulinger
2003-05-18 18:06             ` [OpenAFS-devel] " Pavel Machek
2003-05-13 17:23       ` Trond Myklebust
2003-05-15 11:41         ` Ingo Oeser
2003-05-13 17:42       ` David Howells
2003-05-13 16:03 ` Christoph Hellwig
2003-05-13 16:12   ` David Howells
2003-05-13 20:23     ` Christoph Hellwig
2003-05-13 16:39   ` Jeff Garzik
2003-05-13 16:57     ` David Howells
     [not found] <20030513182950.GB30766@delft.aura.cs.cmu.edu>
2003-05-13 18:53 ` David Howells
  -- strict thread matches above, loose matches on Subject: below --
2003-05-13 15:34 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=8812.1052841957@warthog.warthog \
    --to=dhowells@warthog.cambridge.redhat.com \
    --cc=dhowells@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openafs-devel@openafs.org \
    --cc=torvalds@transmeta.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