All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Smalley <sds@tycho.nsa.gov>
To: "C.J. Adams-Collier KF7BMP" <cjac@colliertech.org>
Cc: Dominick Grift <dominick.grift@gmail.com>,
	SE-Linux <selinux@tycho.nsa.gov>,
	Russell Coker <russell@coker.com.au>
Subject: Re: SELinux on Wheezy
Date: Wed, 08 Feb 2012 15:17:45 -0500	[thread overview]
Message-ID: <1328732265.19254.95.camel@moss-pluto> (raw)
In-Reply-To: <1328730315.5174.1.camel@foxtrot.cjac.ntr.f5net.com>

On Wed, 2012-02-08 at 11:45 -0800, C.J. Adams-Collier KF7BMP wrote:
> > > $ locate xserver.pp
> > > /usr/share/selinux/default/xserver.pp
> > > 
> > > I'll run semodule -i after this morning's reboot.  I installed mutt
> > > yesterday, so I'll work from the console until you folks sign off for
> > > the evening.
> > 
> > I'd suggest installing all of the .pp files to ensure you aren't missing
> > anything else.  The man page for semodule has some examples of how to
> > install all modules from a directory.
> 
> What's the best way to do this at boot?

You just do it once and it remains until/unless you remove it with
semodule -r.  No need to do it on each boot.  Normally it is done when
you install the policy package, but since your policy package apparently
didn't install all modules, I'm suggesting that you do so manually.  

cd /usr/share/selinux/default
ls *.pp | grep -Ev "base.pp|enableaudit.pp" | xargs /usr/sbin/semodule -b base.pp -i
should install them all.

-- 
Stephen Smalley
National Security Agency


--
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:[~2012-02-08 20:17 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-06  4:26 SELinux on Wheezy C.J. Adams-Collier KF7BMP
2012-02-06 15:39 ` Stephen Smalley
2012-02-06 16:17   ` C.J. Adams-Collier KF7BMP
2012-02-06 23:23     ` C.J. Adams-Collier KF7BMP
2012-02-06 23:48       ` Dominick Grift
2012-02-07 17:42       ` Stephen Smalley
2012-02-07 18:44         ` Dominick Grift
2012-02-07 18:55         ` C.J. Adams-Collier KF7BMP
2012-02-09 13:17       ` Russell Coker
2012-02-06 15:56 ` Dominick Grift
2012-02-06 16:21   ` C.J. Adams-Collier KF7BMP
2012-02-07 17:35     ` C.J. Adams-Collier KF7BMP
2012-02-07 17:47       ` Stephen Smalley
2012-02-07 18:56         ` C.J. Adams-Collier KF7BMP
2012-02-07 20:02           ` C.J. Adams-Collier
2012-02-07 20:08             ` Stephen Smalley
2012-02-07 21:05               ` C.J. Adams-Collier
2012-02-08 13:24                 ` Stephen Smalley
2012-02-08 17:39                   ` C.J. Adams-Collier KF7BMP
2012-02-08 17:54                     ` Stephen Smalley
2012-02-08 19:45                       ` C.J. Adams-Collier KF7BMP
2012-02-08 20:17                         ` Stephen Smalley [this message]
2012-02-08 21:32                           ` C.J. Adams-Collier KF7BMP
2012-02-09 13:08                             ` Russell Coker
2012-02-09 13:55                             ` Stephen Smalley
2012-02-09 17:34                               ` C.J. Adams-Collier KF7BMP
2012-02-09 17:53                                 ` Stephen Smalley
2012-02-09 13:05                     ` Russell Coker
2012-02-09 16:40                       ` C.J. Adams-Collier KF7BMP
2012-02-09 13:12     ` Russell Coker

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=1328732265.19254.95.camel@moss-pluto \
    --to=sds@tycho.nsa.gov \
    --cc=cjac@colliertech.org \
    --cc=dominick.grift@gmail.com \
    --cc=russell@coker.com.au \
    --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.