All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Scroggins <dataefx@earthlink.net>
To: "Benjamin D. Thomas" <ben@linuxsecurity.com>
Cc: Christopher Mahmood <ckm@suse.com>,
	"SELinux@tycho.nsa.gov" <SELinux@tycho.nsa.gov>
Subject: Re: [Fwd: Partial TOC for Comment]
Date: Fri, 17 Aug 2001 12:00:29 -0700	[thread overview]
Message-ID: <3B7D69CD.2EC446B1@earthlink.net> (raw)
In-Reply-To: 20010817172038.46E2811D317@juggernaut.guardiandigital.com

"Benjamin D. Thomas" wrote:
> 
> > In summary, I think you need to tell not only how to set it up
> > and configure it and what the theory is behind it, but also
> > how to use it.
> 
> Yes, agreed.  I like the format of the document and what you have is
> great.  I just think it is missing sections on installation,
> configuration, and common issues.  I realize that documents of this sort
> have been written, but they should be compiled into this single document.
> 
> Thanks,
> 
> Ben

Thanks, all this input is great.. 

I was thinking along these lines -- due to the fact that SELinux already
has an INSTALL document, I was talking with a few people about scripting
a major portion of the commands, then possibly have some one work one a
UI similar to the kernel menuconfig dialog screen for editing the policy
files. I also believe this is the place to add the following items:

1) Getting the Kernel Source 
2) Editing the Policy Files (integrate the UI feature here) 
3) Building the Kernel (scripted to a single command like Debian
"makekpkg") and Related Tools
4) Relabeling the Filesystem (have a script which parses the contents of
the default file vs. current filesystem and edits or deletes the
appropriate entries) 

If we can get these to fly, then the amount of redundancy would be
limited.

--
You have received this message because you are subscribed to the selinux 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:[~2001-08-17 19:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-17  2:07 [Fwd: Partial TOC for Comment] John Scroggins
2001-08-16 23:12 ` Dale Amon
     [not found]   ` <3B7D591A.EA28B00C@earthlink.net>
2001-08-17 11:23     ` Dale Amon
2001-08-18 11:43       ` LeRoy Cressy
     [not found]         ` <20010818084601.A7060@vnl.com>
     [not found]           ` <3B7FD0EE.398E6F02@telocity.com>
2001-08-19  4:58             ` Dale Amon
2001-08-17 17:20   ` Benjamin D. Thomas
2001-08-17 19:00     ` John Scroggins [this message]
2001-08-17 17:37   ` Conan Callen
2001-08-17 20:05     ` John Scroggins
2001-08-16 23:18 ` Dale Amon
2001-08-17 18:03 ` Conan Callen
2001-08-17 19:51   ` John Scroggins
2001-08-17 20:09     ` Conan Callen
2001-08-17 11:42       ` Dale Amon
2001-08-17 22:21       ` John Scroggins

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=3B7D69CD.2EC446B1@earthlink.net \
    --to=dataefx@earthlink.net \
    --cc=SELinux@tycho.nsa.gov \
    --cc=ben@linuxsecurity.com \
    --cc=ckm@suse.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.