From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from jazzdrum.ncsc.mil (zombie.ncsc.mil [144.51.88.131]) by tarius.tycho.ncsc.mil (8.13.1/8.13.1) with ESMTP id k6V1Bp1J001753 for ; Sun, 30 Jul 2006 21:11:51 -0400 Received: from mx1.redhat.com (jazzdrum.ncsc.mil [144.51.5.7]) by jazzdrum.ncsc.mil (8.12.10/8.12.10) with ESMTP id k6V1BhQ1011662 for ; Mon, 31 Jul 2006 01:11:45 GMT From: "David O'Brien" To: fedora-selinux-list-request@redhat.com, "NSA_SELinux List" , "redhat-lspp@redhat.com" Subject: Re: RHEL5 Security Guide draft TOC for review/comment Date: Mon, 31 Jul 2006 11:11:39 +1000 Cc: David Howells , Forrest Taylor , Harald Hoyer , James Morris , Karsten Wade , Nalin Dahyabhai , Stephen John Smoogen , Stephen Smalley , Thomas Woerner , Tomas Mraz , Ulrich Drepper References: <200607281151.46191.daobrien@redhat.com> In-Reply-To: <200607281151.46191.daobrien@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Message-Id: <200607311111.40188.daobrien@redhat.com> Sender: owner-selinux@tycho.nsa.gov List-Id: selinux@tycho.nsa.gov top posting... I've received a number of replies to this, offering suggestions and review time, etc. Thanks to all. I'll start collating comments and suggestions from everyone and put together a revised TOC. I have a number of volunteers for SELinux, which is great, so I'll have to ask that people nominate a "focus-area", be it Policy, Troubleshooting, End-user Control, Administrator Control, whatever. That way people can check out the appropriate file and have their way with it, without fear of treading on toes. thanks everyone for the feedback and offers to help. David On Friday 28 July 2006 11:51, David O'Brien wrote: > Firstly, apologies if you receive this twice. I'm casting a wide net... > > I've attached the draft TOC of the Red Hat Enterprise Linux 5 Security > Guide for all to review and comment on. (Despite appearances it's not > supposed to be a valid xml file; I wrote it that way for my own > convenience.) As mentioned in the Scope Statement (attached), this is the > integration of the RHEL4 Security Guide and the SELinux Guide. Our focus > for this release is on accuracy and use cases, at the expense of low-level > details. > > Please feel free to make any suggestions about structure, topics, etc., how > we could use/enhance this info from other areas (Training?) or vice versa. > > I have a few names down for reviewers, authors/editors, etc., (see comments > in file) but am looking for more. If there is an area where you feel you > could contribute, please put your hand up. All contributors will be > acknowledged and included in the colophon, and earn our undying gratitude. > :-) > > cheers -- 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.