mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kyle Moffett <mrmacman_g4@mac.com>
To: linux-kernel@vger.kernel.org
Subject: In-kernel Authentication Tokens (PAGs)
Date: Fri, 11 Jun 2004 22:37:36 -0400	[thread overview]
Message-ID: <772741DF-BC19-11D8-888F-000393ACC76E@mac.com> (raw)

I am working on a generic PAG subsystem for the kernel, something that
handles BLOB PAG data and could be used for OpenAFS, Coda, NFSv4, etc.
I have a patch, but it is not well tested yet.  Here is an overview of 
the
architecture:

Each process has a PAG, and each PAG has a parent PAG.  Users are
allowed to make new PAGs associated with their UID and modify ones that
are already associated with their UID.  Each PAG consists of a set of 
tokens,
each uniquely identified by an integral "type" and a string "realm."  
The
search for a token by any subsystem is done starting at the immediate 
parent
and proceeds upward.  Tokens are in kernel memory and so are not ever
swapped out.

Each PAG is represented in user-space as an integer.  Here are the 
sys-calls
that I propose:

sys_get_pag
sys_set_pag
	These manipulate the PAG associated with a given PID.

sys_get_pag_parent
sys_set_pag_parent
	These manipulate the parent PAG of a given PAG

sys_get_pag_uid
sys_set_pag_uid
	These manipulate the UID which "owns" a PAG

sys_get_pag_token
sys_set_pag_token
	These manipulate tokens within a specific PAG

sys_search_pag_token
	This executes the search process as described above

Cheers,
Kyle Moffett


             reply	other threads:[~2004-06-12  2:37 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-12  2:37 Kyle Moffett [this message]
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
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=772741DF-BC19-11D8-888F-000393ACC76E@mac.com \
    --to=mrmacman_g4@mac.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®