From: "David O'Brien" <daobrien@redhat.com>
To: SELinux internal list <rhselinux-project@redhat.com>,
SELinux Mailing List <selinux@tycho.nsa.gov>
Subject: Request for info: development status of SELinux and Security in general
Date: Mon, 17 Jul 2006 14:56:13 +1000 [thread overview]
Message-ID: <200607171456.13378.daobrien@redhat.com> (raw)
As some of you know, I'm currently involved in updating the Security
Guide/SELinux Guide for RHEL5. We're putting together a TOC from which we'll
determine exactly which topics we can effectively document for this release.
What would really help is information on SELinux development and kernel
development directly related to security that is ongoing and still has some
way to go before completion, and areas that are unlikely to change (or change
any more) for RHEL5.
I've been watching the "Summary of current SELinux work" thread (among many
others) on rhselinux-project@redhat.com but what would be good is to know
what work is actually completed or near completion. Is there somewhere I can
look this up or otherwise track progress?
I know this is a big ask but any pointers, etc., would be greatly appreciated.
thanks
--
David O'Brien
Red Hat Asia Pacific Pty Ltd
Tel: +61-7-3514-8189
Fax: +61-7-3514-8199
email: daobrien@redhat.com
web: http://apac.redhat.com/
--
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.
reply other threads:[~2006-07-17 4:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200607171456.13378.daobrien@redhat.com \
--to=daobrien@redhat.com \
--cc=rhselinux-project@redhat.com \
--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.