From: Stephen Smalley <sds@tycho.nsa.gov>
To: Paul Moore <paul@paul-moore.com>,
"Stepan G. Fedorov" <stfedorov@gmail.com>
Cc: Selinux@tycho.nsa.gov
Subject: Re: semanage interface has no effect
Date: Mon, 25 Aug 2014 10:36:04 -0400 [thread overview]
Message-ID: <53FB49D4.8050802@tycho.nsa.gov> (raw)
In-Reply-To: <CAHC9VhSwgERb2NoY8vK3nT=wxBh7fyaD7ECGoxcRij5P6u1XKQ@mail.gmail.com>
On 08/25/2014 10:30 AM, Paul Moore wrote:
> On Mon, Aug 25, 2014 at 10:00 AM, Stepan G. Fedorov <stfedorov@gmail.com> wrote:
>> 25.08.2014 17:10, Stephen Smalley пишет:
>>
>>> Legacy network checks are gone; use peer labeling or secmark instead,
>>> http://paulmoore.livejournal.com/tag/documentation
>>
>>
>> Thank you for quick reply!
>>
>> In case of "just installed" system, where no iptables SECMARK rules present,
>> and no labeled packets arrive on network interface - what will be selinux
>> contexts of all incoming packets?
>
> In this case the incoming packets would be labeled "unlabeled_t", just
> like any other unlabeled data on the system.
...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.
next prev parent reply other threads:[~2014-08-25 14:36 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 [this message]
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=53FB49D4.8050802@tycho.nsa.gov \
--to=sds@tycho.nsa.gov \
--cc=Selinux@tycho.nsa.gov \
--cc=paul@paul-moore.com \
--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.