From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH v2 1/1] Support LDAP backend infrastructure
Date: Tue, 6 Mar 2012 09:06:27 -0500 [thread overview]
Message-ID: <4F5619E3.8040106@tresys.com> (raw)
In-Reply-To: <20120301200255.GA17815@siphos.be>
On 03/01/12 15:02, Sven Vermeulen wrote:
> The DHCP daemon supports LDAP backends (next to its file-based backend).
> This patch adds support for this through the dhcp_use_ldap boolean. We also
> allow the DHCP daemon to bind to generic UDP ports (needed by ISC BIND proper
> startup).
>
> Signed-off-by: Sven Vermeulen <sven.vermeulen@siphos.be>
> ---
> dhcp.te | 11 +++++++++++
> 1 files changed, 11 insertions(+), 0 deletions(-)
>
> diff --git a/dhcp.te b/dhcp.te
> index d4424ad..ab04a3d 100644
> --- a/dhcp.te
> +++ b/dhcp.te
> @@ -4,6 +4,12 @@ policy_module(dhcp, 1.9.0)
> #
> # Declarations
> #
> +## <desc>
> +## <p>
> +## Enable LDAP backend support for DHCP daemon.
> +## </p>
> +## </desc>
> +gen_tunable(dhcp_use_ldap, false)
>
> type dhcpd_t;
> type dhcpd_exec_t;
> @@ -68,6 +74,7 @@ corenet_tcp_bind_generic_node(dhcpd_t)
> corenet_udp_bind_generic_node(dhcpd_t)
> corenet_tcp_bind_dhcpd_port(dhcpd_t)
> corenet_udp_bind_dhcpd_port(dhcpd_t)
> +corenet_udp_bind_generic_port(dhcpd_t)
Looks like a port needs to be defined.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2012-03-06 14:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 20:02 [refpolicy] [PATCH v2 1/1] Support LDAP backend infrastructure Sven Vermeulen
2012-03-06 14:06 ` Christopher J. PeBenito [this message]
2012-03-06 20:10 ` Sven Vermeulen
2012-03-06 20:54 ` Sven Vermeulen
2012-03-12 13:09 ` Christopher J. PeBenito
2012-03-12 13:11 ` 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=4F5619E3.8040106@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.