From: "Lorenzo Hernández García-Hierro" <lorenzo@gnu.org>
To: russell@coker.com.au
Cc: Luke Kenneth Casson Leighton <lkcl@lkcl.net>,
Colin Walters <walters@verbum.org>,
Manoj Srivastava <manoj.srivastava@stdc.com>,
selinux@tycho.nsa.gov, debian-devel@lists.debian.org
Subject: Re: Updated SELinux Release
Date: Mon, 03 Jan 2005 15:47:57 +0100 [thread overview]
Message-ID: <1104763677.4281.9.camel@localhost.localdomain> (raw)
In-Reply-To: <200501032353.12543.russell@coker.com.au>
[-- Attachment #1: Type: text/plain, Size: 1862 bytes --]
Hi Russell,
El lun, 03-01-2005 a las 23:53 +1100, Russell Coker escribió:
> On Saturday 06 November 2004 02:57, Luke Kenneth Casson Leighton
> <lkcl@lkcl.net> wrote:
> > debian doesn't GIVE users that choice [remember the adamantix
> > bun-fight, anyone?] and instead settles for about the lowest possible
> > common denominator - no consideration to modern security AT ALL!
>
> Doing the things that Adamantix does takes some work. The Adamantix people
> are doing their own distribution and are not contributing to Debian. There
> are many Debian developers who want to see the same stuff included in Debian
> (including me), but no-one with the right combination of interest, time, and
> skills.
>
> If someone is looking for things to work on then it would be a good place to
> start.
I think that Hardened Debian is putting many efforts in terms of
security technologies deployment.
We are now working on the deployment in Ubuntu Linux as a first move
before the possible deployment in Debian.
I'm now interested in making SELinux a really reliable solution thus i
have the other things almost done, and some kernel work is already done.
The debian policies should be improved and creation of a work team would
be great.
I have a blank page at the wiki
(http://wiki.debian-hardened.org/SELinux_on_Debian) which could be a
start point.
As i'm new and even i don't know what's the current state of SELinux
Debian deployment, i would appreciate any information.
I've set up a site (BTW, running on a hardened debian powered "box")
where i'm maintaining patches and other stuff i worked on related with
SELinux, it's at http://selinux.tuxedo-es.org .
Cheers,
--
Lorenzo Hernández García-Hierro <lorenzo@gnu.org> [1024D/6F2B2DEC]
[2048g/9AE91A22] Hardened Debian head developer & project manager
[-- Attachment #2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-01-06 1:50 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-03 15:39 Updated SELinux Release Stephen Smalley
2004-11-03 18:19 ` Karl MacMillan
2004-11-03 19:21 ` Dhruv Gami
2004-11-04 2:15 ` Colin Walters
2004-11-04 7:02 ` Manoj Srivastava
2004-11-04 13:15 ` Luke Kenneth Casson Leighton
2004-11-05 4:06 ` Colin Walters
2004-11-05 10:28 ` Luke Kenneth Casson Leighton
2004-11-05 15:11 ` Colin Walters
2004-11-05 15:51 ` Stephen Smalley
2004-11-05 15:57 ` Luke Kenneth Casson Leighton
2004-11-05 21:01 ` Colin Walters
2005-01-03 12:53 ` Russell Coker
2005-01-03 14:47 ` Lorenzo Hernández García-Hierro [this message]
2004-11-05 12:29 ` Stephen Smalley
2004-11-04 14:35 ` Stephen Smalley
2004-11-04 15:38 ` James Morris
2004-11-04 15:47 ` Stephen Smalley
2004-11-04 14:24 ` Stephen Smalley
2004-11-04 0:59 ` Manoj Srivastava
2004-11-04 3:37 ` Colin Walters
2004-11-04 6:57 ` Manoj Srivastava
2004-11-04 13:38 ` Stephen Smalley
2004-11-04 18:25 ` Christopher J. PeBenito
2004-11-04 18:25 ` Stephen Smalley
2004-11-04 13:33 ` Stephen Smalley
-- strict thread matches above, loose matches on Subject: below --
2005-03-09 21:02 Stephen Smalley
2005-06-22 18:57 ` Stephen Smalley
2005-09-07 16:23 ` Stephen Smalley
2005-01-07 20:59 Stephen Smalley
2004-08-19 19:01 Updated SELinux release Stephen Smalley
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=1104763677.4281.9.camel@localhost.localdomain \
--to=lorenzo@gnu.org \
--cc=debian-devel@lists.debian.org \
--cc=lkcl@lkcl.net \
--cc=manoj.srivastava@stdc.com \
--cc=russell@coker.com.au \
--cc=selinux@tycho.nsa.gov \
--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.