On 5/6/06, Petre Rodan <[EMAIL PROTECTED]> wrote:
> -Petre Rodan wrote: "use what we have now in the stable branch please"
> [So is that a package in portage then?] Sorry if I'm being dense here.
it means use the stable version of the toolchain ( sys-apps/checkpolicy
sys-apps/policycoreutils sys-libs/libsepol sys-libs/libselinux
sys-libs/libsemanage dev-python/python-selinux ) and the policies we now have
in sec-policy/*.
and even if there will be a serefpolicy release, you are asked not to blindly
migrate your production servers/whatever without a thorough test.
> -How far along is the work to migrate to the reference policy?
all policies except clockspeed is now in the upstream repository.
So what's the status of Gentoo SELinux these days? The handbook seems
to be updated in the last month, so I guess it's not dead. Just hard
for me (as a non-dev) to see much going on. I have noticed though that
glibc-2.4 and gcc-4 are still masked, which makes me think this is
what was previously referred to by a "non-broken toolchain"? Or are
migration problems the real issue (based on comments in package.mask)?
Are anywhere close to having a selinux/2006.1 profile or is 2007.0
more realistic? And for a new installation, it looks like it might be
best to avoid 2006.1 in favor of 2006.0 or earlier, since 2006.1 has
glibc-2.4 and gcc-4.1.
--
This message has been scanned for memes and
dangerous content by MindScanner, and is
believed to be unclean.
--
[email protected] mailing list
