public inbox for gentoo-hardened@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sven Vermeulen <sven.vermeulen@siphos.be>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] Feedback on article recommending Gentoo for SELinux
Date: Mon, 13 Jul 2015 15:02:55 +0200	[thread overview]
Message-ID: <CAPzO=NzaDScPiRcfR5VLatc+pDR_F4PZCHKeDwgVNNa0-B3wUw@mail.gmail.com> (raw)
In-Reply-To: <20150713113133.GA17362@meriadoc.Home>

On Mon, Jul 13, 2015 at 1:31 PM, Jason Zaman <perfinion@gentoo.org> wrote:
> Overall a good article. One thing which I would also point out together
> with the move to CIL is that there is now no "base" module. In the 2.3
> and earlier userlands, all the important things were in "base.pp" and
> then other things were added separately as modules. One of the reasons
> why modifying ports works in the 2.4 userland is that there is no more
> base, it is treated just like any other module now so the limitations of
> eg ports must be in base no longer apply.

I'd be careful with the "no base". This heavily depends on how the
userland utilities will work with the CIL, which isn't fully clarified
yet.

> Secondly, related to "poor support for preserving local changes across
> system updates". The tools now have the concept of priority so users can
> easy completely replace a distro-provided module at a higher priority
> (semodule -X 900 -i foo.pp). I haven't (yet) updated our selinux eclass
> to install at a lower priority but will hopefully do that soon.

We work with the default 400 (100 is for the migrated modules). Do you
see a reason why we have to explicitly support a particular priority
in our eclass?

Wkr,
  Sven Vermeulen


  reply	other threads:[~2015-07-13 13:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-12 23:46 [gentoo-hardened] Feedback on article recommending Gentoo for SELinux S. Lockwood-Childs
2015-07-13 11:31 ` Jason Zaman
2015-07-13 13:02   ` Sven Vermeulen [this message]
2015-07-13 13:51     ` Jason Zaman
2015-07-13 16:50       ` Sven Vermeulen
2015-07-13 17:02 ` Sven Vermeulen
2015-07-15  5:35 ` S. Lockwood-Childs

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='CAPzO=NzaDScPiRcfR5VLatc+pDR_F4PZCHKeDwgVNNa0-B3wUw@mail.gmail.com' \
    --to=sven.vermeulen@siphos.be \
    --cc=gentoo-hardened@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox