From: mgrepl@redhat.com (Miroslav Grepl)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] system_daemontools.patch
Date: Fri, 05 Mar 2010 09:05:10 +0100 [thread overview]
Message-ID: <4B90BB36.2020704@redhat.com> (raw)
In-Reply-To: <4B8FDDAC.7010101@redhat.com>
On 03/04/2010 05:19 PM, Daniel J Walsh wrote:
> On 03/04/2010 11:16 AM, Christopher J. PeBenito wrote:
>> On Tue, 2010-02-23 at 17:01 -0500, Daniel J Walsh wrote:
>>> http://people.fedoraproject.org/~dwalsh/SELinux/F13/system_daemontools.patch
>>>
>>>
>>> + daemonstools_run_start(sysadm_t, sysadm_r)
>>> + daemontools_search_svc_dir(syslogd_t)
>>> + daemontools_sigchld_run(ucspitcp_t)
>>>
>>> svc_run needs sys_resource
>>> reads urand
>>>
>>> writes to console
>>>
>>> Other access required.
>> Why is this network access needed:
>>
>> +allow svc_start_t self:tcp_socket create_stream_socket_perms;
>> +corenet_tcp_bind_generic_node(svc_start_t)
>> +corenet_tcp_bind_generic_port(svc_start_t)
>>
>> a quick glance through the code didn't indicate any network access.
>>
> I have no idea. I did not write this one. Miroslav or Dominick?
Ok, I am a culprit. We got this as a part of bug and people needed to
add a local module with these rules to fix policy issues.
Regards,
Miroslav
next prev parent reply other threads:[~2010-03-05 8:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 22:01 [refpolicy] system_daemontools.patch Daniel J Walsh
2010-03-04 16:16 ` Christopher J. PeBenito
2010-03-04 16:19 ` Daniel J Walsh
2010-03-04 17:36 ` Dominick Grift
2010-03-05 8:05 ` Miroslav Grepl [this message]
2010-03-08 13:47 ` Christopher J. PeBenito
-- strict thread matches above, loose matches on Subject: below --
2010-08-26 23:30 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=4B90BB36.2020704@redhat.com \
--to=mgrepl@redhat.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.