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] SELinux and no-multilib
Date: Sun, 27 Mar 2011 21:42:18 +0200	[thread overview]
Message-ID: <20110327194217.GA29814@siphos.be> (raw)
In-Reply-To: <4D83E2E6.3010505@gentoo.org>

On Fri, Mar 18, 2011 at 06:55:34PM -0400, Anthony G. Basile wrote:
> You're not wrong, but this can be restructured to come better in line
> with the rest of the hardened profiles.  I have to do a careful analysis
> of the stacking and see if we can get something similar out of simpler
> stackings and then fix up what might be missed in the final layers of
> the stack.

My suggestion would be to

1. stabilize the current set of policies
2. remove the policies whose version is >= 3.0 (including those -2008* ones)
3. make a "features/selinux" profile (which contains all SELinux relevant
   aspects but is not a real profile in its own)
4. Create sublocations within the existing profiles for SELinux (like 
   hardened/linux/amd64/selinux and hardened/linux/amd64/no-multilib/selinux) 

These sublocations would only have a single file called "parent" showing
something like:
  ../
  ../../../../features/selinux

I just tried this on my no-multilib system as well as on a multilib one, and
apart from USE="gdbm bzip2 urandom nptl justify -fortran" I have had no
other changes (checked the different outputs of "emerge --info" as well as a
"emerge -puDN world").

Wkr,
	Sven Vermeulen



  reply	other threads:[~2011-03-27 19:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-18  6:12 [gentoo-hardened] SELinux and no-multilib Sven Vermeulen
2011-03-18 11:41 ` Anthony G. Basile
2011-03-18 15:43   ` Sven Vermeulen
2011-03-18 22:55     ` Anthony G. Basile
2011-03-27 19:42       ` Sven Vermeulen [this message]
2011-03-27 20:28         ` Anthony G. Basile

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=20110327194217.GA29814@siphos.be \
    --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