From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH] sysnetwork: dhcpc binds socket to random high udp ports sysnetwork: do not audit attempts by ifconfig to read, and write dhcpc udp sockets (looks like a leaked fd)
Date: Fri, 27 Sep 2013 17:05:10 -0400 [thread overview]
Message-ID: <5245F306.5090204@tresys.com> (raw)
In-Reply-To: <1380274541-28793-1-git-send-email-dominick.grift@gmail.com>
On Fri 27 Sep 2013 05:35:41 AM EDT, Dominick Grift wrote:
>
> Signed-off-by: Dominick Grift <dominick.grift@gmail.com>
> diff --git a/policy/modules/system/sysnetwork.te b/policy/modules/system/sysnetwork.te
> index 9476a7e..9fbb331 100644
> --- a/policy/modules/system/sysnetwork.te
> +++ b/policy/modules/system/sysnetwork.te
> @@ -111,7 +111,9 @@
> corenet_udp_bind_dhcpc_port(dhcpc_t)
> corenet_tcp_connect_all_ports(dhcpc_t)
> corenet_sendrecv_dhcpd_client_packets(dhcpc_t)
> -corenet_sendrecv_dhcpc_server_packets(dhcpc_t)
> +
> +corenet_sendrecv_all_server_packets(dhcpc_t)
> +corenet_udp_bind_all_unreserved_ports(dhcpc_t)
I'm anxious about allowing. Which dhcpc is doing this?
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2013-09-27 21:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 9:35 [refpolicy] [PATCH] sysnetwork: dhcpc binds socket to random high udp ports sysnetwork: do not audit attempts by ifconfig to read, and write dhcpc udp sockets (looks like a leaked fd) Dominick Grift
2013-09-27 21:05 ` Christopher J. PeBenito [this message]
2013-09-27 21:09 ` Dominick Grift
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=5245F306.5090204@tresys.com \
--to=cpebenito@tresys.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.