From: dominick.grift@gmail.com (Dominick Grift)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH/RFC 2/2] Add minidlna policy
Date: Thu, 02 May 2013 17:41:25 +0200 [thread overview]
Message-ID: <1367509285.27309.34.camel@d30> (raw)
In-Reply-To: <20130501183845.GC25116@siphos.be>
On Wed, 2013-05-01 at 20:38 +0200, Sven Vermeulen wrote:
> +corenet_sendrecv_ssdp_client_packets(minidlna_t)
> +corenet_sendrecv_ssdp_server_packets(minidlna_t)
> +
> +corenet_tcp_bind_generic_node(minidlna_t)
> +corenet_tcp_sendrecv_generic_if(minidlna_t)
> +corenet_tcp_sendrecv_generic_node(minidlna_t)
> +
> +corenet_udp_bind_generic_node(minidlna_t)
> +corenet_udp_bind_ssdp_port(minidlna_t)
> +
> +corenet_sendrecv_trivnet1_client_packets(minidlna_t)
> +corenet_sendrecv_trivnet1_server_packets(minidlna_t)
> +corenet_tcp_bind_trivnet1_port(minidlna_t)
> +
Another oversight
You do not need the "client_packets" interface calls if the domain does
not connect to the port
In this case minidlna domain only binds tcp sockets to trivnet1 ports,
and udp sockets to ssdp ports
i think we also need these:
corenet_tcp_sendrecv_trivnet1_port(minidlna_t)
corenet_udp_sendrecv_ssdp_port(minidlna_t)
next prev parent reply other threads:[~2013-05-02 15:41 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 [this message]
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
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=1367509285.27309.34.camel@d30 \
--to=dominick.grift@gmail.com \
--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.