All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dominick Grift <domg472@gmail.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Cheyenne Solo <ayla.cheyenne@gmail.com>,
	selinux@tycho.nsa.gov, Daniel J Walsh <dwalsh@redhat.com>,
	"Christopher J. PeBenito" <cpebenito@tresys.com>
Subject: Re: Base module, modules.conf
Date: Fri, 16 Jan 2009 20:23:12 +0100	[thread overview]
Message-ID: <1232133792.8594.4.camel@localhost.localdomain> (raw)
In-Reply-To: <1232132620.13917.109.camel@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 540 bytes --]

On Fri, 2009-01-16 at 14:03 -0500, Stephen Smalley wrote:

> You need to first obtain a policy source tree as your starting point.
> If you want to minimize your divergence from the distro-shipped policy,
> then download the selinux-policy source RPM (.src.rpm) for your distro,
> expand it, and then customize as desired and rebuild it (Dan - is there
> a recipe documented somewhere for doing that?). 

I have created a screen cast that focuses on just that. However, the
file is 200MB and i do not have the ability to host it.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-01-16 19:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-16 17:43 Base module, modules.conf Cheyenne Solo
2009-01-16 19:03 ` Stephen Smalley
2009-01-16 19:23   ` Dominick Grift [this message]
2009-01-16 19:52     ` Stephen Smalley
2009-01-19 20:53       ` Jacques Thomas
2009-01-20 14:26         ` Stephen Smalley
2009-01-20 15:58           ` Joe Nall
2009-01-20 19:25             ` Stephen Smalley
2009-01-20 20:31               ` Jacques Thomas
2009-02-04 20:52   ` Cheyenne Solo
2009-02-04 21:53     ` Dominick Grift
2009-02-05 17:51     ` 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=1232133792.8594.4.camel@localhost.localdomain \
    --to=domg472@gmail.com \
    --cc=ayla.cheyenne@gmail.com \
    --cc=cpebenito@tresys.com \
    --cc=dwalsh@redhat.com \
    --cc=sds@tycho.nsa.gov \
    --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.