From: Bradley Chapman <kakadu@gmail.com>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: selinux@tycho.nsa.gov, russell@coker.com.au
Subject: Re: An SELinux policy for Red Hat 9
Date: Fri, 9 Jul 2004 15:52:00 +0100 [thread overview]
Message-ID: <e294b46e0407090752b199eeb@mail.gmail.com> (raw)
In-Reply-To: <1089375253.11726.34.camel@moss-spartans.epoch.ncsc.mil>
Mr. Smalley,
On Fri, 09 Jul 2004 08:14:13 -0400, Stephen Smalley <sds@epoch.ncsc.mil> wrote:
>
>
> On Fri, 2004-07-09 at 07:43, Bradley Chapman wrote:
> > On Fri, 9 Jul 2004 21:11:55 +1000, Russell Coker <russell@coker.com.au> wrote:
> > > But if you REALLY want to use RHL 9, the current policy should work OK, you
> > > just have to make the appropriate changes to pam, logrotate, cron, coreutils,
> > > etc.
> >
> > What sort of changes? Path changes?
>
> I think Russell is referring to the userland patches for those
> packages. The current patches and SRPMS in our userland tree are drawn
> from the Fedora Core development tree, so you are likely to run into
> dependency problems building them on RH9. And Fedora Core actually
> includes _many_ other patched userland packages for SELinux; we only
> maintain a core subset in our tree for reference purposes for people who
> want to port to other distributions. A few examples of patched userland
> packages in Fedora Core that are not in our tree include gdm, usermode,
> atd, and libuser, and there are many others. There is also the issue of
> glibc security awareness; the RH9 glibc won't enable secure mode upon
> domain transitions, unlike the Fedora Core glibc.
Oh.
I thought the patches mentioned were confined mostly to core system
utilities; I had no idea that FC2's modifications for SELlinux were
quite that extensive!
>
> If you truly are limited to using RH9, then you should likely grab an
> older release of SELinux that was based on RH9. But life will be
> simpler if you can move to FC2.
Well, in light of your recommendations, I will certainly consider such
a move now.
If I do decide to move to FC2, how difficult will it then become to
adapt the SELinux policy
to my needs?
>
> --
> Stephen Smalley <sds@epoch.ncsc.mil>
> National Security Agency
>
Brad
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2004-07-09 14:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-08 20:17 An SELinux policy for Red Hat 9 Bradley Chapman
2004-07-09 11:11 ` Russell Coker
2004-07-09 11:43 ` Bradley Chapman
2004-07-09 12:14 ` Stephen Smalley
2004-07-09 14:52 ` Bradley Chapman [this message]
2004-07-09 16:22 ` Stephen Smalley
2004-07-09 17:30 ` Valdis.Kletnieks
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=e294b46e0407090752b199eeb@mail.gmail.com \
--to=kakadu@gmail.com \
--cc=russell@coker.com.au \
--cc=sds@epoch.ncsc.mil \
--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.