All of lore.kernel.org
 help / color / mirror / Atom feed
From: Diyab <diyab@diyab.net>
To: Kerry Thompson <kerry@crypt.gen.nz>
Cc: SELinux Mail List <selinux@tycho.nsa.gov>
Subject: Re: SELinux on Slackware 9 with PAM
Date: Mon, 18 Aug 2003 13:23:20 -0400	[thread overview]
Message-ID: <3F410B88.7090809@diyab.net> (raw)
In-Reply-To: <3357.202.27.185.71.1061177252.squirrel@www.crypt.gen.nz>

Kerry Thompson wrote:
> I just got around to reading this, after carrying it around with me for
> almost a week now.
> 
> Its very useful document for anyone deploying SELinux on Slackware. The
> document pretty much follows the README and describes what changes need to
> be made for Slackware.
> 
> A few comments:
> 
> - you should mention that the Vixie crond in the SE release has been
> modified for SELinux and really needs to be installed if you want cron.
> Alternatively the user would need to modify Dillon's crond code to support
> the SELinux extensions.

I do kind of mention how it is modified just not in the introduction 
where I explain the changing of cronds.  I can fix that, it's just that 
I don't imagine many people running a machine without a crond of some sort.

> 
> - you don't seem to configure the kernel ( make menuconfig, or edit
> .config ) before compiling it - which may cause problems if the user has
> devices not in the standard config.
> 

In the instructions I direct the user to start at the "Step-by-Step 
Building and Installing" section and continue until they hit step one. 
The text between the step-by-step title and step one details applying 
the SELinux patch to the kernel tree as well as configuring and building 
the kernel.

> - be careful about specifying line numbers when describing changes to
> files - the line numbers will probably change in new releases of
> Slack/SELinux.

The line numbers won't be a problem even if the policies change since 
the policy will still compile.  I don't really see a better way to do 
this and still keep it simple for the reader though.  Did you have 
something in mind?

> 
> - I recommend converting the document to HTML, even if you just wrap <Hx>
> tages around the headers. Search engines give preference to keywords in
> HTML files and headers.

I had planned on this I just haven't had the time yet.  I made the 
initial document text so that everyone could read it no matter what they 
were using.  The PDF version is available now also.

> All in all a very useful document. Anyone installing on Slackware will
> save themselves a lot of time by referring to this.
> 
> Kerry
> 

Thanks for your feedback Kerry.

Timothy,

-- 
I put instant coffee in a microwave and almost went back in time.
		-- Steven Wright


--
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.

      parent reply	other threads:[~2003-08-18 17:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-12  7:26 SELinux on Slackware 9 with PAM Diyab
2003-08-18  3:27 ` Kerry Thompson
2003-08-18  5:10   ` Russell Coker
2003-08-18 17:29     ` Diyab
2003-08-18 17:23   ` Diyab [this message]

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=3F410B88.7090809@diyab.net \
    --to=diyab@diyab.net \
    --cc=kerry@crypt.gen.nz \
    --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.