All of lore.kernel.org
 help / color / mirror / Atom feed
From: Glenn Faden <Glenn.Faden@sun.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Thomas Liu <tliu@redhat.com>,
	selinux@tycho.nsa.gov, jmorris@namei.org, eparis@parisplace.org
Subject: Re: [PATCH 1/2 -v3] Namespacing of security/selinux
Date: Fri, 14 Aug 2009 10:28:34 -0700	[thread overview]
Message-ID: <4A859EC2.2030807@sun.com> (raw)
In-Reply-To: <1250263220.3629.34.camel@moss-pluto.epoch.ncsc.mil>

Stephen Smalley wrote:
> On Tue, 2009-07-07 at 17:49 -0400, Thomas Liu wrote:
>   
>> This includes namespacing of all items originally labeled
>> security_ with sel_.
>>
>> In addition, the functions sel_netif_sid and security_netif_sid
>> have been renamed because the namespacing would cause a conflict.
>>
>> sel_netif_sid has been renamed to sel_netif_sid_by_index, and
>> security_netif_sid has been renamed to sel_netif_sid_by_name
>>     
>
> This patch has a minor reject against the current security-testing tree.
>
> However, I'm having second thoughts about the renaming idea.  There are
> a rather large number of documents, not to mention the userspace API,
> that talk about security_compute_av() and friends, and thus I'm a bit
> hesitant to render them all obsolete.
>   
Changing the namespace from security_ to sel_ or selinux_ makes it more 
difficult for Solaris and other non-linux systems which may be 
supporting Flask, to be compatible at the library level with policy 
management applications.

--Glenn

--
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-08-14 17:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-06 18:58 [PATCH 1/4 -v2] Namespacing of security/selinux Thomas Liu
2009-07-06 19:43 ` Stephen Smalley
2009-07-07 12:06   ` Stephen Smalley
2009-07-07 12:48     ` James Morris
2009-07-07 17:47       ` Eric Paris
2009-07-07 21:49     ` [PATCH 1/2 -v3] " Thomas Liu
2009-08-14 15:20       ` Stephen Smalley
2009-08-14 15:20         ` Eric Paris
2009-08-14 17:28         ` Glenn Faden [this message]
2009-08-14 17:47           ` Stephen Smalley
2009-07-06 20:28 ` [PATCH 1/4 -v2] " Paul Moore

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=4A859EC2.2030807@sun.com \
    --to=glenn.faden@sun.com \
    --cc=eparis@parisplace.org \
    --cc=jmorris@namei.org \
    --cc=sds@tycho.nsa.gov \
    --cc=selinux@tycho.nsa.gov \
    --cc=tliu@redhat.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 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.