From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 1/1] hostname daemon init hostname from dhcpcd, try 2
Date: Thu, 06 Jan 2011 08:03:51 -0500 [thread overview]
Message-ID: <4D25BDB7.6050103@tresys.com> (raw)
In-Reply-To: <4D24C7B3.1000004@giz-works.com>
On 01/05/11 14:34, Chris Richards wrote:
> On 01/05/2011 09:33 AM, Christopher J. PeBenito wrote:
>> On 12/20/10 17:29, gizmo at giz-works.com wrote:
>>> From: Chris Richards<gizmo@giz-works.com>
>>>
>>> Allow the hostname daemon to configure the system hostname according
>>> to information obtained from dhcpcd DHCP Client daemon.
>> Are you sure these aren't from a leaked fd?
>>
> Not 100%, no. How would I tell?
Did you try dontauditing it? If its leaked it would work without the
access.
>>> Signed-off-by: Chris Richards<gizmo@giz-works.com>
>>> ---
>>> policy/modules/system/hostname.te | 2 ++
>>> 1 files changed, 2 insertions(+), 0 deletions(-)
>>>
>>> diff --git a/policy/modules/system/hostname.te b/policy/modules/system/hostname.te
>>> index c310775..8509560 100644
>>> --- a/policy/modules/system/hostname.te
>>> +++ b/policy/modules/system/hostname.te
>>> @@ -49,6 +49,8 @@ init_use_script_ptys(hostname_t)
>>>
>>> logging_send_syslog_msg(hostname_t)
>>>
>>> +sysnet_rw_dhcpc_stream_sockets(hostname_t)
>>> +
>>> miscfiles_read_localization(hostname_t)
>>>
>>> sysnet_read_config(hostname_t)
>>
>
> _______________________________________________
> refpolicy mailing list
> refpolicy at oss.tresys.com
> http://oss.tresys.com/mailman/listinfo/refpolicy
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2011-01-06 13:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 22:29 [refpolicy] [PATCH 1/1] hostname daemon init hostname from dhcpcd, try 2 gizmo at giz-works.com
2011-01-05 15:33 ` Christopher J. PeBenito
2011-01-05 19:34 ` Chris Richards
2011-01-06 13:03 ` Christopher J. PeBenito [this message]
2011-01-07 7:00 ` Chris Richards
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=4D25BDB7.6050103@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.