From: sven.vermeulen@siphos.be (Sven Vermeulen)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH/RFC 2/2] Add minidlna policy
Date: Fri, 3 May 2013 19:21:50 +0200 [thread overview]
Message-ID: <20130503172150.GA15138@siphos.be> (raw)
In-Reply-To: <5183BFEE.1030309@tresys.com>
On Fri, May 03, 2013 at 09:47:26AM -0400, Christopher J. PeBenito wrote:
> As you mentioned in a latter email, compat_net has been removed. The SELinux network access controls are only SECMARK now.
>
[...]
> Yes. I think what you're confused on is that SECMARK labels are local only. They are not transferred over the network like labeled IPSEC or NetLabel/CIPSO. The object class for those labels is peer. The only remaining permissions on port types is name_bind and name_connect.
So for each port type that we declare, the corenet_{tcp,udp}_sendrecv_*_port
is actually void now? Only corenet_{tcp,udp}_{bind,connect}_*_port is then
used?
It starts making sense.
Even if SECMARK is used, the bind/connect is still needed, right?
Wkr,
Sven Vermeulen
next prev parent reply other threads:[~2013-05-03 17:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 18:36 [refpolicy] [PATCH/RFC 0/2] Introduce minidlna policy Sven Vermeulen
2013-05-01 18:37 ` [refpolicy] [PATCH/RFC 1/2] Add trivnet1 port (8200) Sven Vermeulen
2013-05-01 18:38 ` [refpolicy] [PATCH/RFC 2/2] Add minidlna policy Sven Vermeulen
2013-05-01 19:12 ` Dominick Grift
2013-05-01 20:09 ` Sven Vermeulen
2013-05-01 20:14 ` Dominick Grift
2013-05-02 18:26 ` Christopher J. PeBenito
2013-05-02 10:59 ` Dominick Grift
2013-05-02 15:41 ` Dominick Grift
2013-05-02 19:23 ` Sven Vermeulen
2013-05-02 19:52 ` Dominick Grift
2013-05-03 7:08 ` Dominick Grift
2013-05-03 12:02 ` Sven Vermeulen
2013-05-03 12:19 ` Dominick Grift
2013-05-03 12:23 ` Dominick Grift
2013-05-03 13:47 ` Christopher J. PeBenito
2013-05-03 17:21 ` Sven Vermeulen [this message]
2013-05-03 17:38 ` Christopher J. PeBenito
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=20130503172150.GA15138@siphos.be \
--to=sven.vermeulen@siphos.be \
--cc=refpolicy@oss.tresys.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.