All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Smalley <sds@tycho.nsa.gov>
To: "C.J. Adams-Collier" <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 08:24:30 -0500	[thread overview]
Message-ID: <1328707470.19254.16.camel@moss-pluto> (raw)
In-Reply-To: <20120207210501.GE18478@colliertech.org>

On Tue, 2012-02-07 at 13:05 -0800, C.J. Adams-Collier wrote:
> cjac@foxtrot:~$ sudo which seinfo
> cjac@foxtrot:~$ apt-file search seinfo | grep bin | wc -l
> 0

seinfo is part of the setools package.

> Sounds reasonable.  Do I get policy from my distribution, or should I
> generate one myself?

Normally from your distribution, assuming the selinux packages for
Debian are still being maintained.

IIRC, the Debian selinux policy package tries to minimize the set of
installed policy modules based on the set of installed packages, but
that isn't an exact mapping and might be leaving you without a complete
policy.  Whereas Fedora installs all policy modules unconditionally.

If the .pp files are on your filesystem and just not installed into the
policy store, you can manually add them by running semodule -i on them.
Try listing the files installed from your policy packages and see if
xserver.pp is among them.  

> cjac@foxtrot:~$ dpkg -l | grep selinux-policy
> ii  selinux-policy-default               2:2.20110726-3                 Strict and Targeted variants of the SELinux policy
> ii  selinux-policy-dev                   2:2.20110726-3                 Headers from the SELinux reference policy for building modules
> ii  selinux-policy-doc                   2:2.20110726-3                 Documentation for the SELinux reference policy
> 
> cjac@foxtrot:~$ apt-cache search selinux-policy
> selinux-policy-default - Strict and Targeted variants of the SELinux policy
> selinux-policy-dev - Headers from the SELinux reference policy for building modules
> selinux-policy-doc - Documentation for the SELinux reference policy
> selinux-policy-mls - MLS (Multi Level Security) variant of the SELinux policy
> selinux-policy-src - Source of the SELinux reference policy for customization
> 
> If I'm going to generate one myself, I need to understand them a bit
> better.  I would like anything I generate to be useable by the rest of
> the Debian world.  There seem to be some examples I ran review in the
> selinux-policy-doc and selinux-policy-mls packages.
> 
> Regarding re-labeling, every time I boot without the selinux arguments
> to my kernel and then boot with them, the filesystem seems to get
> re-labeled.  Is there a better way to do this?

On Fedora, you could touch /.autorelabel or pass "autorelabel" on the
kernel command line to force a relabel at boot.  You can also run
fixfiles relabel as a command after booting.  No need to disable SELinux
and then re-enable it.

-- 
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 13:24 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 [this message]
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
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=1328707470.19254.16.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.