From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] refpolicy or vendor supplied version ?
Date: Wed, 12 Feb 2014 08:37:39 -0500 [thread overview]
Message-ID: <52FB7923.8060305@tresys.com> (raw)
In-Reply-To: <1392160726.2480.YahooMailNeo@web120201.mail.ne1.yahoo.com>
On 02/11/14 18:18, John Joe wrote:
> I plan to start implementing selinux and for this I need to write custom policies for the specific set of software that we run. After developing 1-2 policies and have read the mailing list I started to wonder what is best to go on long run with refpolicy or with selinux packages that come with rhel 6?
If you simply want to add your custom policies on top of a base policy that makes the core system work, then either would work. Both have long term support for RHEL6. If you want to customize the base policy, it may be a little more difficult of a question. What goals do you have for your policy?
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
prev parent reply other threads:[~2014-02-12 13:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 23:18 [refpolicy] refpolicy or vendor supplied version ? John Joe
2014-02-12 13:37 ` Christopher J. PeBenito [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=52FB7923.8060305@tresys.com \
--to=cpebenito@tresys.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.