From: "Lorenzo Hernández García-Hierro" <lorenzo@gnu.org>
To: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Cc: Colin Walters <walters@verbum.org>,
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 19:30:42 +0100 [thread overview]
Message-ID: <1111775442.27644.144.camel@localhost.localdomain> (raw)
In-Reply-To: <20050325175904.GP8553@lkcl.net>
[-- Attachment #1: Type: text/plain, Size: 1452 bytes --]
El vie, 25-03-2005 a las 17:59 +0000, Luke Kenneth Casson Leighton
escribió:
> On Fri, Mar 25, 2005 at 10:31:32AM -0500, Colin Walters wrote:
>
> > 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.
>
> about six/eight months ago, i worked for about four months on
> getting debian to work with selinux (strict).
>
> including getting udev to work (with tmpfs).
>
> so, likewise, i'd be happy to help.
Great, there's a page on the wiki that might be a start point:
http://www.ubuntulinux.org/wiki/SELinux
just write your name there if you want to (formerly) contribute.
By now, the "TODO" is there.
> many of the patches are delayed until sarge is released, at which point
> libselinux1 can be made "Required" rather than "Optional".
Right, Ubuntu Breezy (Hoary+1) is our target, and sure that we can have
many work done for it.
Then such work could get back into Debian, as in many other fields of
the project.
> at _that_ point, the patch floodgates open, and patches to coreutils
> etc. can be put forward.
I hope so ;)
Thanks, cheers.
--
Lorenzo Hernández García-Hierro <lorenzo@gnu.org>
[1024D/6F2B2DEC] & [2048g/9AE91A22][http://tuxedo-es.org]
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-03-25 18: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
2005-03-25 17:59 ` Luke Kenneth Casson Leighton
2005-03-25 18:30 ` Lorenzo Hernández García-Hierro [this message]
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=1111775442.27644.144.camel@localhost.localdomain \
--to=lorenzo@gnu.org \
--cc=lkcl@lkcl.net \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=ubuntu-hardened@lists.ubuntu.com \
--cc=walters@verbum.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 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.