From: "Javier J. Martínez Cabezón" <tazok.id0@gmail.com>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] Subject: Hardened Gentoo RSBAC deprecation and removal notice
Date: Mon, 29 Dec 2008 06:42:05 +0100 [thread overview]
Message-ID: <897813410812282142p763fb224r7002ec6c919c1f20@mail.gmail.com> (raw)
In-Reply-To: <200812281825.55730.gengor@gentoo.org>
Why do you want to remove all rsbac related documentation?, I think is
a non-sense to do this. Documentation does not harm anybody and in
case of rsbac is almost nonexistent .
I'm an rsbac user (maybe one of the last) and a gentoo hardened one, I
have never used gentoo rsbac ebuilds, so for me is not any kind of
change.
Maybe you could put your opinion in the main page of the mandatory
access controls related (something like rsbac is not longer maintained
in gentoo so we suggest you to change to by this reason and this one
and this one.... blahblahblah).
2008/12/29 Gordon Malm <gengor@gentoo.org>:
> Hi all,
>
> Hardened Gentoo has been without an RSBAC maintainer for quite a long time
> now.
>
> Support for RSBAC in Hardened Gentoo is discontinued effective immediately.
> RSBAC-related ebuilds, bugs and documents will begin being purged starting
> January 31st, 2009.
>
> All users of RSBAC in Hardened Gentoo who require mandatory or role based
> access control are strongly encouraged to migrate to Grsecurity's RBAC or
> SELinux at this time. Anyone wishing to continue using RSBAC will be without
> support from the Hardened Gentoo project.
>
> The RSBAC project itself continues as normal @ http://www.rsbac.org.
>
> Sincerely,
> Gordon Malm (gengor)
>
>
next prev parent reply other threads:[~2008-12-29 5:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 2:25 [gentoo-hardened] Subject: Hardened Gentoo RSBAC deprecation and removal notice Gordon Malm
2008-12-29 5:42 ` Javier J. Martínez Cabezón [this message]
2008-12-29 8:28 ` Gordon Malm
2008-12-29 15:39 ` Javier J. Martínez Cabezón
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=897813410812282142p763fb224r7002ec6c919c1f20@mail.gmail.com \
--to=tazok.id0@gmail.com \
--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