All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: Alternative user management approach
Date: Sat, 25 Jun 2005 06:28:30 -0400	[thread overview]
Message-ID: <42BD31CE.9090908@redhat.com> (raw)
In-Reply-To: <20050624225217.97028.qmail@web31614.mail.mud.yahoo.com>

Ok this all sounds good, but how do we come to a consensus. 

Do we need an "role attribute" to define "user" roles.

roleattribute staff_r user;
roleattribute user_r user;
roleattribute sysadm_r user;

Then do we need a mechanism in policy to associate roles with "user" roles?

How does all this work with MLS ranges?

Should we have a brainstorming session?  It is important to us (Red Hat) 
that we get this settled soon.

Do we have a new file which associates uids to user roles?

Dan


-- 



--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  reply	other threads:[~2005-06-25 10:26 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-24 16:02 Alternative user management approach Karl MacMillan
2005-06-24 16:38 ` Casey Schaufler
2005-06-24 17:04   ` Karl MacMillan
2005-06-24 17:25     ` Casey Schaufler
2005-06-24 17:30       ` Karl MacMillan
2005-06-24 19:34     ` Stephen Smalley
2005-06-24 18:09 ` Brian T. Sniffen
2005-06-24 18:21   ` Stephen Smalley
2005-06-24 19:50     ` James Morris
2005-06-24 19:58       ` Stephen Smalley
2005-06-24 23:23         ` James Morris
2005-06-26 16:13       ` Russell Coker
2005-06-24 18:32   ` Ivan Gyurdiev
2005-06-24 18:41     ` Karl MacMillan
2005-06-24 22:11       ` Valdis.Kletnieks
2005-06-24 22:52         ` Casey Schaufler
2005-06-25 10:28           ` Daniel J Walsh [this message]
2005-06-25 15:37             ` Joshua Brindle
2005-06-25 16:34               ` Casey Schaufler
2005-06-25 19:37               ` Ivan Gyurdiev
2005-06-25 19:49                 ` Ivan Gyurdiev
2005-06-26 16:38                 ` Russell Coker
2005-06-26 20:17                   ` Ivan Gyurdiev
2005-06-25 20:02               ` Daniel J Walsh
2005-06-27 14:59                 ` Joshua Brindle
2005-06-26 16:36             ` Russell Coker
2005-06-26 17:46               ` Casey Schaufler
2005-06-27  2:24                 ` Russell Coker
2005-06-27  2:43                   ` Casey Schaufler
2005-06-27  3:43                     ` Russell Coker
2005-06-27 15:32                       ` Casey Schaufler
2005-06-27 22:32                         ` Russell Coker
2005-06-28 12:44                           ` Frank Mayer
2005-06-28 15:24                             ` Casey Schaufler
2005-06-26 16:11       ` Russell Coker
2005-06-24 18:10 ` Ivan Gyurdiev
2005-06-24 18:29   ` Ivan Gyurdiev
2005-06-24 18:36     ` Karl MacMillan
2005-06-24 18:52       ` Ivan Gyurdiev
2005-06-24 19:23         ` Stephen Smalley
2005-06-24 19:01       ` Stephen Smalley
2005-06-24 19:21         ` Ivan Gyurdiev
2005-06-24 19:40           ` Stephen Smalley
2005-06-24 18:19 ` Stephen Smalley
2005-06-24 18:38   ` Karl MacMillan
  -- strict thread matches above, loose matches on Subject: below --
2005-06-28 14:43 Chad Hanson

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=42BD31CE.9090908@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=selinux@tycho.nsa.gov \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.