All of lore.kernel.org
 help / color / mirror / Atom feed
From: domg472@gmail.com (Dominick Grift)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 2/2] DHCPC daemon init network interface, try 2
Date: Mon, 20 Dec 2010 23:31:03 +0100	[thread overview]
Message-ID: <4D0FD927.3000608@gmail.com> (raw)
In-Reply-To: <1292884142-6568-1-git-send-email-gizmo@giz-works.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/20/2010 11:29 PM, gizmo at giz-works.com wrote:
> From: Chris Richards <gizmo@giz-works.com>
> 
> Allow dhcpcd DCHP 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.te |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/policy/modules/system/sysnetwork.te b/policy/modules/system/sysnetwork.te
> index dfbe736..e0838f8 100644
> --- a/policy/modules/system/sysnetwork.te
> +++ b/policy/modules/system/sysnetwork.te
> @@ -50,7 +50,7 @@ allow dhcpc_t self:fifo_file rw_fifo_file_perms;
>  allow dhcpc_t self:tcp_socket create_stream_socket_perms;
>  allow dhcpc_t self:udp_socket create_socket_perms;
>  allow dhcpc_t self:packet_socket create_socket_perms;
> -allow dhcpc_t self:netlink_route_socket { create_socket_perms nlmsg_read };

i might be wrong but are you sure that "r_netlink_socket_perms" is not
enough?

> +allow dhcpc_t self:netlink_route_socket create_netlink_socket_perms;
>  
>  allow dhcpc_t dhcp_etc_t:dir list_dir_perms;
>  read_lnk_files_pattern(dhcpc_t, dhcp_etc_t, dhcp_etc_t)
> @@ -81,7 +81,7 @@ domtrans_pattern(dhcpc_t, ifconfig_exec_t, ifconfig_t)
>  
>  kernel_read_system_state(dhcpc_t)
>  kernel_read_network_state(dhcpc_t)
> -kernel_search_network_sysctl(dhcpc_t)
> +kernel_rw_network_sysctls(dhcpc_t)
>  kernel_read_kernel_sysctls(dhcpc_t)
>  kernel_request_load_module(dhcpc_t)
>  kernel_use_fds(dhcpc_t)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAk0P2ScACgkQMlxVo39jgT/teQCfdnnCbA+ITSPZKuvdAnD42CEP
W08AnjJaxtrNINdPc9hz+qlYb+8iXwnH
=MijZ
-----END PGP SIGNATURE-----

  reply	other threads:[~2010-12-20 22:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-20 22:29 [refpolicy] [PATCH 2/2] DHCPC daemon init network interface, try 2 gizmo at giz-works.com
2010-12-20 22:31 ` Dominick Grift [this message]
2010-12-21 13:47   ` Daniel J Walsh

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=4D0FD927.3000608@gmail.com \
    --to=domg472@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.