From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 1/2] DHCPC daemon init network interface
Date: Wed, 15 Dec 2010 15:02:27 -0500 [thread overview]
Message-ID: <4D091ED3.80107@tresys.com> (raw)
In-Reply-To: <1290933932-9193-1-git-send-email-gizmo@giz-works.com>
On 11/28/10 03:45, Chris Richards wrote:
> Allow dhcpcd DHCP Client daemon to start. Add interface to allow
> hostname daemon to talk to dhcpcd.
>
> Signed-off-by: Chris Richards <gizmo@giz-works.com>
> ---
> policy/modules/system/sysnetwork.if | 19 +++++++++++++++++++
> 1 files changed, 19 insertions(+), 0 deletions(-)
>
> diff --git a/policy/modules/system/sysnetwork.if b/policy/modules/system/sysnetwork.if
> index 8e71fb7..73bb9e8 100644
> --- a/policy/modules/system/sysnetwork.if
> +++ b/policy/modules/system/sysnetwork.if
> @@ -196,6 +196,24 @@ interface(`sysnet_dbus_chat_dhcpc',`
>
> ########################################
> ## <summary>
> +## Read and write the dhcp client unix
> +## stream socket
> +## </summary>
> +## <param name="domain">
> +## <summary>
> +## Domain allowed access.
> +## </summary>
> +## </param>
> +#
> +interface(`sysnet_rw_stream_sockets_dhcpc',`
sysnet_rw_dhcpc_stream_sockets()
> + gen_require(`
> + type dhcpc_t;
> + ')
> + allow $1 dhcpc_t:unix_stream_socket { read write };
> +')
> +
> +########################################
> +## <summary>
> ## Read and write dhcp configuration files.
> ## </summary>
> ## <param name="domain">
> @@ -711,3 +729,4 @@ interface(`sysnet_use_portmap',`
>
> sysnet_read_config($1)
> ')
> +
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
prev parent reply other threads:[~2010-12-15 20:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-28 8:45 [refpolicy] [PATCH 1/2] DHCPC daemon init network interface Chris Richards
2010-12-15 20:02 ` Christopher J. PeBenito [this message]
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=4D091ED3.80107@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.