From: Dominick Grift <dac.override@gmail.com>
To: selinux@tycho.nsa.gov
Subject: Re: [RFC] Split up policycoreutils
Date: Mon, 24 Oct 2016 15:16:16 +0200 [thread overview]
Message-ID: <218ba91e-3c97-6896-9c0b-a214b9a047a1@gmail.com> (raw)
In-Reply-To: <db994f8e-27d9-7554-56f5-beb217274d1b@tycho.nsa.gov>
[-- Attachment #1.1: Type: text/plain, Size: 2074 bytes --]
On 10/24/2016 03:13 PM, Stephen Smalley wrote:
> On 10/22/2016 09:44 AM, Chris PeBenito wrote:
>> On 10/21/16 13:47, Stephen Smalley wrote:
>>> policycoreutils started life as a small set of utilities that were
>>> necessary or at least widely used in production on a SELinux system.
>>> Over time though it has grown to include many optional components, and
>>> even within a given subdirectory (e.g. sepolicy) there seem to be a
>>> number of components that should be optional (e.g. the dbus service).
>>> I'd like to propose that we move a number of components out of
>>> policycoreutils into their own top-level subdirectory (possibly grouping
>>> some of the related ones together).
>>
>> I'm not sure where the main part of sepolicy should go, but it would be
>> nice to split it out since it depends on setools which has heavier
>> dependencies than a core system package should typically have IMO
>> (NetworkX, which pulls in scipy, numpy, matplotlib, etc.)
>
> I would be in favor of that too, but hesitated to do so because it would
> require moving audit2allow and semanage out of policycoreutils as well.
> Fedora does package those as part of policycoreutils-python (along with
> sepolgen). Arguably audit2allow isn't necessary for production (but
> many users of SELinux in Linux distributions rely on it), but semanage
> is more fundamental these days.
>
> However, if people are open to moving sepolicy, audit2allow, and
> semanage, possibly combining them with sepolgen in a new
> subdirectory/package, then we could explore that.
>
Yes please. These aren't needed or feasible in a CIL only config
>
> _______________________________________________
> Selinux mailing list
> Selinux@tycho.nsa.gov
> To unsubscribe, send email to Selinux-leave@tycho.nsa.gov.
> To get help, send an email containing "help" to Selinux-request@tycho.nsa.gov.
>
--
Key fingerprint = 5F4D 3CDB D3F8 3652 FBD8 02D5 3B6C 5F1D 2C7B 6B02
https://sks-keyservers.net/pks/lookup?op=get&search=0x3B6C5F1D2C7B6B02
Dominick Grift
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 648 bytes --]
next prev parent reply other threads:[~2016-10-24 13:16 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 17:47 [RFC] Split up policycoreutils Stephen Smalley
2016-10-21 18:11 ` Daniel J Walsh
2016-10-21 21:06 ` Paul Moore
2016-10-22 13:44 ` Chris PeBenito
2016-10-24 13:13 ` Stephen Smalley
2016-10-24 13:16 ` Dominick Grift [this message]
2016-10-24 13:21 ` Stephen Smalley
2016-10-24 21:15 ` Daniel J Walsh
2016-10-25 5:47 ` Dominick Grift
2016-10-31 9:27 ` Sven Vermeulen
2016-10-31 14:29 ` Stephen Smalley
2016-10-25 3:49 ` Jason Zaman
2016-10-25 22:12 ` Chris PeBenito
2016-10-24 9:28 ` Petr Lautrbach
2016-10-24 12:33 ` Sven Vermeulen
2016-10-31 18:05 ` Stephen Smalley
2016-10-31 18:11 ` Dominick Grift
[not found] ` <eaeb9dc4-e69f-47de-50ad-083ce97e1153@gmail.com>
[not found] ` <98931665-f141-29e3-fb3a-9335e58874b0@tycho.nsa.gov>
2016-10-31 18:26 ` Dominick Grift
2016-10-31 18:42 ` Stephen Smalley
2016-11-01 19:00 ` Daniel J Walsh
2016-11-08 19:42 ` Stephen Smalley
2016-11-14 20:41 ` Jason Zaman
2016-11-15 14:47 ` Stephen Smalley
2016-11-15 15:01 ` Stephen Smalley
2016-11-15 16:30 ` Jason Zaman
2016-11-16 19:00 ` Stephen Smalley
2016-11-16 19:07 ` Stephen Smalley
2016-11-18 12:40 ` Daniel J Walsh
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=218ba91e-3c97-6896-9c0b-a214b9a047a1@gmail.com \
--to=dac.override@gmail.com \
--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.