From: Daniel J Walsh <dwalsh@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Ivan Valeriev Gyurdiev <ivg2@cornell.edu>,
SELinux List <selinux@tycho.nsa.gov>,
Joshua Brindle <jbrindle@tresys.com>
Subject: Re: [SEMANAGE] Rename seuser -> seuser_local
Date: Wed, 25 Jan 2006 15:51:10 -0500 [thread overview]
Message-ID: <43D7E4BE.5060506@redhat.com> (raw)
In-Reply-To: <1138212699.13075.27.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley wrote:
> On Wed, 2006-01-25 at 12:55 -0500, Daniel J Walsh wrote:
>
>> No, and if they did we could do it via semanage.
>>
>
> Yes, that was my expectation.
>
>
>>> It seems to me that this could be a desirable capability in the future.
>>> Also, remember that this means that the user can apply non-additive
>>> changes to the seuser file - in other words, the delete function will
>>> clear not only local changes, but will completely remove the __default__,
>>> or root user if requested, reverting back to libselinux defaults (not
>>> post-script defaults). Not sure if this is a good idea...
>>>
>>>
>>>
>> Yes this would be bad.
>>
>
> It wouldn't be a good idea for them to do that, but I'm not sure we need
> to introduce this additional baggage just to idiot-proof semanage.
>
>
How about I idiotproof seobject.py?
>>> The current naming scheme seemed inconsistent, which is why I sent a patch
>>> for it. Whether or not a .system file is added, the rename improves
>>> consistency with current usage - places seusers function in the _local
>>> namespace where they belong.
>>>
>
> I don't want API changes without adequate justification. Yes, we still
> have flexibility in this arena since we control all users of the
> library, but we still don't want arbitrary changes.
>
>
--
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.
next prev parent reply other threads:[~2006-01-25 20:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-20 23:34 [SEMANAGE] Rename seuser -> seuser_local Ivan Gyurdiev
2006-01-23 12:52 ` Stephen Smalley
2006-01-25 16:07 ` Ivan Valeriev Gyurdiev
2006-01-25 16:28 ` Stephen Smalley
2006-01-25 17:31 ` Ivan Valeriev Gyurdiev
2006-01-25 17:55 ` Daniel J Walsh
2006-01-25 18:11 ` Stephen Smalley
2006-01-25 20:51 ` Daniel J Walsh [this message]
2006-01-25 21:05 ` Ivan Valeriev Gyurdiev
2006-01-27 20:52 ` Stephen Smalley
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=43D7E4BE.5060506@redhat.com \
--to=dwalsh@redhat.com \
--cc=ivg2@cornell.edu \
--cc=jbrindle@tresys.com \
--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.