All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karl MacMillan <kmacmillan@mentalrootkit.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: selinux@tycho.nsa.gov
Subject: Re: [RFC] Drop setlocaldefs support from trunk (2.x series)
Date: Fri, 23 Feb 2007 10:59:09 -0500	[thread overview]
Message-ID: <45DF0F4D.7090104@mentalrootkit.com> (raw)
In-Reply-To: <1172237335.19041.17.camel@moss-spartans.epoch.ncsc.mil>

Stephen Smalley wrote:
> On Thu, 2007-02-22 at 16:53 -0500, Karl MacMillan wrote:
>> Stephen Smalley wrote:
>>> Hi,
>>>
>>> With the migration to libsemanage and managed policy, the setlocaldefs
>>> support in libselinux and underlying support in libsepol for parsing
>>> local booleans and users files is obsolete in modern SELinux
>>> distributions.  Ideally, I'd like to drop it out entirely from the trunk
>>> (2.x series), while preserving it on the stable branch (1.x series).
>>> Specifically, this would mean:
>>> - Removing setlocaldefs support from libselinux,
>>> - Removing sepol_genusers and sepol_genbools and their internal logic
>>> from libsepol, including the legacy config file parsers there.
>>> sepol_genbools_array() would remain due to its use for preserving
>>> actives booleans upon policy reload, but it doesn't require the config
>>> file parser.
>>>
>> That's fine with me, though I question whether the config parsers might 
>> not be better in libsepol than in libsemanage.
> 
> Here we are talking about config parsers for the local booleans file and
> local user definitions, all of which now live in libsemanage and are
> private to it.  Not config parsers for the base policy per se.
> 

My thinking was that future versions of that file might be binary or in 
a subset of the policy language to avoid special parsers. In that case, 
the code to read those files would likely already be in libsepol. We can 
worry about that if it ever comes about though.

Karl

--
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:[~2007-02-23 15:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-22 16:41 [RFC] Drop setlocaldefs support from trunk (2.x series) Stephen Smalley
2007-02-22 21:53 ` Karl MacMillan
2007-02-23 13:28   ` Stephen Smalley
2007-02-23 15:49     ` Stephen Smalley
2007-02-23 15:59     ` Karl MacMillan [this message]

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=45DF0F4D.7090104@mentalrootkit.com \
    --to=kmacmillan@mentalrootkit.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.