All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Brindle <method@manicmethod.com>
To: Chris PeBenito <pebenito@gentoo.org>
Cc: Daniel J Walsh <dwalsh@redhat.com>,
	SE Linux <selinux@tycho.nsa.gov>,
	Chad Sellers <csellers@tresys.com>,
	Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: This patch add seusers support to SELinux
Date: Wed, 24 Jun 2009 17:10:45 -0400	[thread overview]
Message-ID: <4A429655.1020306@manicmethod.com> (raw)
In-Reply-To: <1245442170.3574.23.camel@defiant.pebenito.net>

Chris PeBenito wrote:
> On Fri, 2009-06-19 at 15:51 -0400, Daniel J Walsh wrote:
>> On 06/19/2009 03:30 PM, Chris PeBenito wrote:
>>> On Fri, 2009-06-19 at 14:29 -0400, Daniel J Walsh wrote:
>>>> Basically this is the exact same file as the seusers file except it one
>>>> per Linux User where is the seusers file is one record per Linux User.
>>>>
>>>> If I have a distributed environment, I need to say stuff like
>>>>
>>>> engineers logging into people.redhat.com get guest_t:s0
>>>> Admins logging in get unconfined_t:SystemLow-SystemHigh
>>>>
>>>> In addition on some machines dwalsh is an admin and on others he is a
>>>> peon.  So using IPA we generate a mapping from MACHINE to User
>>>>
>>>> dwalsh on dwalsh_laptop gets unconfined_t
>>>> dwalsh on desktop gets user_t
>>>> dwalsh on people gets guest_t
>>>>
>>>> There is a potential use for service but it will probably default to *
>>>> for now.
>>> I don't have a problem with this idea, but I do have a problem with this
>>> not replacing the current seuser behavior.  Having two ways to map linux
>>> users to selinux users is an administration nightmare.  People will be
>>> confused about which one to use and you'll need to know precedence.
>>> What you describe above with the contents of each file just having a *
>>> service would be the same as the current seuser behavior.
>>>
>> Well I don't see administrators editing the new format, we have not even
>> used it yet, since IPA has not shipped this functionality yet.
>
> I don't see how IPA's usage matters.  If we go this way, in the future
> there will be two ways for the seusers mapping, which is confusing.
>

Ping, does anyone else have an opinion on this using the context of the service 
rather than the pam name of the service? I still think the context is more 
appropriate.

Also, if we do this I think we should get rid of the old way of having seusers 
since it isn't clear where to do seuser updates anymore and it isn't even noted 
which of these take precedence.

--
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.

  parent reply	other threads:[~2009-06-24 21:10 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-18 18:20 This patch add seusers support to SELinux Daniel J Walsh
2009-06-18 13:38 ` Joshua Brindle
2009-06-18 13:48   ` Joshua Brindle
2009-06-18 19:37     ` Daniel J Walsh
2009-06-18 19:38     ` Daniel J Walsh
2009-06-18 20:14       ` Joshua Brindle
2009-06-19  9:57         ` Daniel J Walsh
2009-06-19 15:08           ` Joshua Brindle
2009-06-19 15:21             ` Daniel J Walsh
2009-06-19 18:13               ` Joshua Brindle
2009-06-19 18:24                 ` Daniel J Walsh
2009-06-19 18:27                   ` Joshua Brindle
2009-06-19 18:30                     ` Daniel J Walsh
2009-06-19 18:31                       ` Joshua Brindle
2009-06-19 18:39                         ` Daniel J Walsh
2009-06-19 18:29                 ` Daniel J Walsh
2009-06-19 19:30                   ` Chris PeBenito
2009-06-19 19:51                     ` Daniel J Walsh
2009-06-19 20:09                       ` Chris PeBenito
2009-06-22 15:10                         ` Joshua Brindle
2009-06-24 21:10                         ` Joshua Brindle [this message]
2009-06-25 12:31                           ` Stephen Smalley
2009-06-30 15:18               ` Joshua Brindle
2009-07-01 12:44                 ` Daniel J Walsh
2009-07-07 15:50                   ` Joshua Brindle
2009-07-07 16:05                     ` Joshua Brindle
2009-07-07 16:28                       ` Daniel J Walsh
2009-07-07 17:16                         ` Joshua Brindle
2009-07-07 17:27                           ` Daniel J Walsh
2009-07-08 14:05                             ` Joshua Brindle

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=4A429655.1020306@manicmethod.com \
    --to=method@manicmethod.com \
    --cc=csellers@tresys.com \
    --cc=dwalsh@redhat.com \
    --cc=pebenito@gentoo.org \
    --cc=sds@tycho.nsa.gov \
    --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.