From: Russell Coker <russell@coker.com.au>
To: Jag Raman <jag.raman@oracle.com>
Cc: refpolicy <selinux-refpolicy@vger.kernel.org>,
Chris PeBenito <pebenito@ieee.org>
Subject: Re: Testing changes to "refpolicy"
Date: Wed, 10 Apr 2019 10:59:50 +1000 [thread overview]
Message-ID: <4547019.OKaXWVSkba@liv> (raw)
In-Reply-To: <a30c598d-74e0-f3c2-7295-9ac3b1de0947@oracle.com>
On Wednesday, 10 April 2019 1:58:28 AM AEST Jag Raman wrote:
> > There is no official distro for testing. It does support customizations
> > for various distributions (DISTRO build option), but that also depends
> > on how much of the distro's customizations are upstreamed.
>
> I tried setting the "DISTRO" build option to "redhat", and tested on
> Fedora. But it looks like "refpolicy" customizations are not upstream
> for Fedora. It could be because RedHat is maintaining a separate set of
> patches [2] that apply on top of an older version (RELEASE_2_20130424)
> of SELinux refpolicy.
>
> Do you know of any distro whose customizations are upstream?
The vast majority of Debian patches are upstreamed. A couple of months ago I
submitted a lot of patches to get the Debian policy very close to upstream,
the differences at that time were mostly things that upstream didn't agree
with.
Since that time there have been more changes and one particularly noteworthy
thing is that there's been a new release of systemd that needs some changes.
I plan to have all the patches needed for that submitted upstream soon.
If you run Debian/Testing with the upstream policy there is about 10 minutes
work needed to get it all going properly. If you find it more difficult than
that then let me know and I'll fix it.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
prev parent reply other threads:[~2019-04-10 1:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fb70d47d-abb5-7dfd-e0c1-bc8eca28cba8@oracle.com>
2019-04-09 12:02 ` Testing changes to "refpolicy" Chris PeBenito
2019-04-09 15:58 ` Jag Raman
2019-04-10 0:59 ` Russell Coker [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=4547019.OKaXWVSkba@liv \
--to=russell@coker.com.au \
--cc=jag.raman@oracle.com \
--cc=pebenito@ieee.org \
--cc=selinux-refpolicy@vger.kernel.org \
/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.