From: justinmattock@gmail.com (Justin P. Mattock)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Changing build.conf defaults?
Date: Fri, 19 Feb 2010 02:34:29 -0800 [thread overview]
Message-ID: <1266575669.5199.10.camel@linux-dbym.site> (raw)
In-Reply-To: <1266603950.11694.188.camel@gorn.columbia.tresys.com>
On Fri, 2010-02-19 at 13:25 -0500, Christopher J. PeBenito wrote:
> On Fri, 2010-02-19 at 13:00 -0500, Stephen Smalley wrote:
> > Hi,
> >
> > I was wondering whether it would make sense to change the refpolicy
> > build.conf defaults to more closely reflect the actual settings in use
> > in modern distributions. In particular, I was thinking that we are long
> > past the point where it makes sense to make MONOLITHIC=n the default
> > given that:
> > - all modern distros with SELinux use modular/managed policy, and
> > - semodule, semanage, and even setsebool -P will only work if using
> > modular/managed policy these days.
> >
> > Changing the default would eliminate at least one case of common user
> > error when building from upstream refpolicy on a modern distribution.
> >
> > Any objections to changing that default upstream?
>
> I don't. But I'll wait for a while before changing it to see if anyone
> objects.
>
no objections here.
building a binary policy is easier
than monolithic(especially in a distro environment).
i.g. no need for the source to add user/login
just semanage.
Justin P. Mattock
next prev parent reply other threads:[~2010-02-19 10:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 18:00 [refpolicy] Changing build.conf defaults? Stephen Smalley
2010-02-19 18:25 ` Christopher J. PeBenito
2010-02-19 10:34 ` Justin P. Mattock [this message]
2010-02-19 18:43 ` Christopher J. PeBenito
2010-02-19 18:54 ` Justin P. mattock
2010-02-19 19:01 ` Christopher J. PeBenito
2010-02-19 19:32 ` Justin P. mattock
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=1266575669.5199.10.camel@linux-dbym.site \
--to=justinmattock@gmail.com \
--cc=refpolicy@oss.tresys.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.