From: gizmo@giz-works.com (Chris Richards)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 2/2] DHCPC daemon init network interface
Date: Sun, 28 Nov 2010 15:09:06 -0600 [thread overview]
Message-ID: <4CF2C4F2.6080802@giz-works.com> (raw)
In-Reply-To: <20101128101000.GB2234@localhost.localdomain>
Ah, you are correct. I just saw that I could simply add the nlmsg_write
to what was already there and simply added it. I never even thought
about looking to see if there was a macro already defined for that. D'oh!
We'll see if PeBenito wants me to resubmit with the change.
Later,
Chris
On 11/28/2010 04:10 AM, Dominick Grift wrote:
> On Sun, Nov 28, 2010 at 02:45:59AM -0600, Chris Richards wrote:
>> 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..640334d 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 };
>> +allow dhcpc_t self:netlink_route_socket { create_socket_perms nlmsg_read nlmsg_write };
> i am not sure but i suspect we may be able to use create_netlink_socket_perms here
>>
>> 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_net_sysctls(dhcpc_t)
>> kernel_read_kernel_sysctls(dhcpc_t)
>> kernel_request_load_module(dhcpc_t)
>> kernel_use_fds(dhcpc_t)
>> --
>> 1.7.3.2
>>
>> _______________________________________________
>> refpolicy mailing list
>> refpolicy at oss.tresys.com
>> http://oss.tresys.com/mailman/listinfo/refpolicy
> _______________________________________________
> refpolicy mailing list
> refpolicy at oss.tresys.com
> http://oss.tresys.com/mailman/listinfo/refpolicy
>
next prev parent reply other threads:[~2010-11-28 21:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-28 8:45 [refpolicy] [PATCH 2/2] DHCPC daemon init network interface Chris Richards
2010-11-28 10:10 ` Dominick Grift
2010-11-28 21:09 ` Chris Richards [this message]
2010-12-15 20:02 ` 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=4CF2C4F2.6080802@giz-works.com \
--to=gizmo@giz-works.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.