All of lore.kernel.org
 help / color / mirror / Atom feed
From: Colin Walters <walters@verbum.org>
To: "Lorenzo Hernández García-Hierro" <lorenzo@gnu.org>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
	ubuntu-hardened@lists.ubuntu.com, selinux@tycho.nsa.gov
Subject: Re: [RFC] selinux-support (1.0.1) available
Date: Fri, 25 Mar 2005 10:31:32 -0500	[thread overview]
Message-ID: <1111764692.3932.45.camel@nexus.verbum.private> (raw)
In-Reply-To: <1111761662.27644.121.camel@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 2217 bytes --]

On Fri, 2005-03-25 at 15:41 +0100, Lorenzo Hernández García-Hierro
wrote:

> In my opinion, it's going to be Ubuntu specific until it's back-accepted
> in Debian, anyways, I expect to have, at least, the user-land ready for
> SELinux support within the Ubuntu Linux distribution, for the Hoary+1
> release (Breezy).

That's probably reasonable.  If Ubuntu can get SELinux working well on a
Debian-derived system out of the box, it will probably be easier for
Debian to then pull all of the current patches into their distribution.

Nevertheless, I encourage you to work with Debian on this as much as
possible.  SELinux, like any access control system worth something,
requires extensive integration with the rest of the OS.  And core parts
of the OS at that.  You do not want to be deviating much from the Debian
core for packages such as dpkg and coreutils in the long term.  

Also, I strongly suggest that you look at the "targeted" policy shipping
with Fedora.  I had a glance at the Ubuntu wiki page for SELinux and it
seems the proposed policy is "selinux-policy-default", which IIRC is the
"strict" policy.  The experience with Fedora is that strict is not yet
workable as the default for a general-purpose OS, as Ubuntu is.  If you
can get the targeted policy as the Ubuntu default and most importantly
*on* by default, then "Hardened Ubuntu" becomes just s/targeted/strict/,
and perhaps a few other features.  Much less work for the "Hardened"
team.  Getting as many features of "Hardened" into the core should be
your goal anyways; I think that permanently-forked "Hardened" variants
are basically wrong.  They're kind of inherently doomed to be only used
by a very small subset of users.  You want it to be more of a proving
ground or staging area than a fork.

We're doing a lot of work in Fedora to make targeted work well, and I
think we could work together on it to good effect.

I haven't really done any Debian development in a year, but I think I
still remember much of how things work, so I'd be happy to help with any
integration issues you might have.  I'm sure the same is true of
Russell.  Posting to selinux@tycho.nsa.gov is probably your best bet.


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-03-25 15:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-24 22:47 [RFC] selinux-support (1.0.1) available Lorenzo Hernández García-Hierro
2005-03-25 14:08 ` Stephen Smalley
2005-03-25 14:27   ` Stephen Smalley
2005-03-25 18:05     ` Lorenzo Hernández García-Hierro
2005-03-25 19:04       ` Colin Walters
2005-03-25 14:41   ` Lorenzo Hernández García-Hierro
2005-03-25 15:31     ` Colin Walters [this message]
2005-03-25 17:59       ` Luke Kenneth Casson Leighton
2005-03-25 18:30         ` Lorenzo Hernández García-Hierro
2005-03-25 18:13       ` Lorenzo Hernández García-Hierro

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=1111764692.3932.45.camel@nexus.verbum.private \
    --to=walters@verbum.org \
    --cc=lorenzo@gnu.org \
    --cc=sds@tycho.nsa.gov \
    --cc=selinux@tycho.nsa.gov \
    --cc=ubuntu-hardened@lists.ubuntu.com \
    /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.