All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tracy Reed <treed@ultraviolet.org>
To: selinux@tycho.nsa.gov
Subject: Re: MCS error
Date: Thu, 19 Feb 2015 11:33:37 -0800	[thread overview]
Message-ID: <20150219193337.GC12937@tracyreed.org> (raw)
In-Reply-To: <20150219154047.GA11807@linksys-wireless-usb.network2>

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

On Thu, Feb 19, 2015 at 07:40:48AM PST, Dominick Grift spake thusly:
> The MCS implementation has been changed a bit over the years on the policy side.

Is there a RHEL 6 version of the link I pasted below with up to date info?
Lack of documentation and frequent changes rendering documentation obsolete
combined with the inherent complexity of something like this are the main
issues holding back SELinux adoption.

> Back in the earlier day's MCS was enforced on all proceses in redhat distro's by default

Yeah...I actually had it working in a test setup in RHEL 5 but never got it
deployed widely. Now we are trying to redo it with RHEl 6 and running into
issues.

> Nowaday's that is no longer the case, and you need to opt-in for it by associating the mcs_constrained_type type attribute with the type of the process to constrain.
> 
> In rhel6 this attribute name does not exist i suspect. It was renamed to aforementioned later.
> 
> A seinfo -a | grep mcs might reveal the type attribute used for the same in RHEL6. (i think its something with trusted or untrusted, dunno for sure)

I don't follow this part... The seinfo output is:

# seinfo -a | grep mcs
mcssetcats
mcswriteall
mcskillall
mcsreadall
mcsnetwrite
mcsuntrustedproc
mcsptraceall

How do these type attributes relate to MCS?

-- 
Tracy Reed

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2015-02-19 19:33 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-19  1:48 MCS error Tracy Reed
2015-02-19 13:23 ` Stephen Smalley
2015-02-19 15:40   ` Dominick Grift
2015-02-19 19:33     ` Tracy Reed [this message]
2015-02-19 19:46       ` Stephen Smalley
2015-02-19 20:17         ` Tracy Reed
2015-02-19 20:27           ` Stephen Smalley
2015-02-19 21:14           ` Dominick Grift
2015-02-19 20:48       ` Dominick Grift
2015-02-19 21:26         ` Thomas Hurd
2015-02-20  0:34         ` Tracy Reed
2015-02-20  2:02           ` Tracy Reed
2015-02-20  7:33             ` Dominick Grift
2015-02-20 23:27               ` Tracy Reed
2015-02-20 23:38                 ` Joshua Brindle
2015-02-21 13:07                 ` Dominick Grift
2015-02-20 17:44             ` Stephen Smalley
2015-02-20 13:38           ` Stephen Smalley
2015-02-20 16:56             ` Tracy Reed
2015-02-20 17:08               ` Stephen Smalley
2015-02-20 17:33                 ` Stephen Smalley
2015-02-20 22:10                   ` Tracy Reed
2015-02-23 14:43                     ` Stephen Smalley
2015-02-20 22:07                 ` Tracy Reed
2015-02-19 16:19 ` Stephen Smalley
2015-02-19 19:58   ` Tracy Reed
2015-02-19 20:24     ` 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=20150219193337.GC12937@tracyreed.org \
    --to=treed@ultraviolet.org \
    --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.