All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Smalley <sds@tycho.nsa.gov>
To: "Stepan G. Fedorov" <stfedorov@gmail.com>, Selinux@tycho.nsa.gov
Subject: Re: semanage interface has no effect
Date: Mon, 25 Aug 2014 09:10:42 -0400	[thread overview]
Message-ID: <53FB35D2.3030307@tycho.nsa.gov> (raw)
In-Reply-To: <53FB19C7.1040500@gmail.com>

On 08/25/2014 07:11 AM, Stepan G. Fedorov wrote:
> Hello!
> 
> Goal of this experiment is to see allow rules for netif class objects is
> working.
> 
> I use debian wheezy whith MLS selinux policy, in enforced mode.
> 
> eth0 is hte only netwotk interface, except lo.
> 
> sesearch --allow -cnetif shows lots of allow rules for netif_t target
> type / netif target class.
> 
> I do:
>  1) I add new type nginx_http_if_t with my own policy module;
>  2) semanage interface -a -t nginx_http_if_t -r s1:c0.c1023 eth0.
> 
> I expect: to see all the processes in system unable to read/write
> packets from eth0 interface.
> 
> I actually got: nothing changes - all networking is working as it was
> before changing of interface context.
> 
> 
> What am I doing/understanding wrong?

Legacy network checks are gone; use peer labeling or secmark instead,
http://paulmoore.livejournal.com/tag/documentation

  parent reply	other threads:[~2014-08-25 13:10 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 [this message]
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
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=53FB35D2.3030307@tycho.nsa.gov \
    --to=sds@tycho.nsa.gov \
    --cc=Selinux@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.