From: Daniel J Walsh <dwalsh@redhat.com>
To: russell@coker.com.au
Cc: SELinux@tycho.nsa.gov
Subject: Re: named policy patch
Date: Tue, 12 Apr 2005 09:38:09 -0400 [thread overview]
Message-ID: <425BCF41.80403@redhat.com> (raw)
In-Reply-To: <200504122326.33930.russell@coker.com.au>
Russell Coker wrote:
>The attached patch allows named to correctly start on FC4T2 with the strict
>policy when unlimitedRC is commented.
>
>
>
>------------------------------------------------------------------------
>
>diff -u old/named.fc new/named.fc
>--- old/named.fc 2005-04-12 23:24:32.000000000 +1000
>+++ new/named.fc 2005-04-12 23:24:23.000000000 +1000
>@@ -16,6 +16,7 @@
> /etc/rndc.* -- system_u:object_r:named_conf_t
> /etc/rndc.key -- system_u:object_r:dnssec_t
> /usr/sbin/named -- system_u:object_r:named_exec_t
>+/usr/sbin/named-checkconf -- system_u:object_r:named_checkconf_exec_t
> /usr/sbin/r?ndc -- system_u:object_r:ndc_exec_t
> /var/run/ndc -s system_u:object_r:named_var_run_t
> /var/run/bind(/.*)? system_u:object_r:named_var_run_t
>diff -u old/named.te new/named.te
>--- old/named.te 2005-04-12 23:24:39.000000000 +1000
>+++ new/named.te 2005-04-12 23:24:45.000000000 +1000
>@@ -15,6 +15,9 @@
> daemon_domain(named, `, nscd_client_domain')
> tmp_domain(named)
>
>+type named_checkconf_exec_t, file_type, exec_type, sysadmfile;
>+domain_auto_trans(initrc_t, named_checkconf_exec_t, named_t)
>+
> # For /var/run/ndc used in BIND 8
> file_type_auto_trans(named_t, var_run_t, named_var_run_t, sock_file)
>
>
>
Why not just label chckconf as named_exec_t?
--
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2005-04-12 13:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 13:26 named policy patch Russell Coker
2005-04-12 13:38 ` Daniel J Walsh [this message]
2005-04-12 13:56 ` Russell Coker
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=425BCF41.80403@redhat.com \
--to=dwalsh@redhat.com \
--cc=SELinux@tycho.nsa.gov \
--cc=russell@coker.com.au \
/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.