All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: "Stepan G. Fedorov" <stfedorov@gmail.com>,
	Stephen Smalley <sds@tycho.nsa.gov>,
	Paul Moore <paul@paul-moore.com>
Cc: Selinux@tycho.nsa.gov
Subject: Re: semanage interface has no effect
Date: Mon, 25 Aug 2014 11:46:33 -0400	[thread overview]
Message-ID: <53FB5A59.5020805@tresys.com> (raw)
In-Reply-To: <53FB4EC9.4090605@gmail.com>

On 8/25/2014 10:57 AM, Stepan G. Fedorov wrote:
> 
>> ...but the new network permission checks will not be applied
>> until/unless you configure secmark or labeled networking.  Or set the
>> always_check_network policy capability to 1 for secmark, if your kernel
>> supports that.
> 
> Seems I have no such capability. My /sys/fs/selinux/policy_capabilities/
> contains only two files:
> network_peer_controls
> open_perms

That directory only lists the capabilities that are enabled in the
loaded policy.  You need at least a 3.13 kernel and the capability
declared in the policy (in the base module, base.pp).  Distributions
will likely never ship with that capability enabled, as it requires
packet (SECMARK) and peer rules throughout the policy.

-- 
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com

  reply	other threads:[~2014-08-25 15:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-25 11:11 semanage interface has no effect Stepan G. Fedorov
2014-08-25 12:18 ` Dominick Grift
2014-08-25 13:10 ` Stephen Smalley
2014-08-25 14:00   ` Stepan G. Fedorov
2014-08-25 14:30     ` Paul Moore
2014-08-25 14:36       ` Stephen Smalley
2014-08-25 14:57         ` Stepan G. Fedorov
2014-08-25 15:46           ` Christopher J. PeBenito [this message]
2014-08-25 14:46       ` Stepan G. Fedorov
2014-08-25 15:21         ` 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=53FB5A59.5020805@tresys.com \
    --to=cpebenito@tresys.com \
    --cc=Selinux@tycho.nsa.gov \
    --cc=paul@paul-moore.com \
    --cc=sds@tycho.nsa.gov \
    --cc=stfedorov@gmail.com \
    /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.