From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] sudo: Add ldap support for sudoers rules
Date: Mon, 6 Feb 2017 19:54:01 +0100 [thread overview]
Message-ID: <20170206195401.11ccbee3@free-electrons.com> (raw)
In-Reply-To: <1477323263-6689-1-git-send-email-cdf123@cdf123.net>
Hello,
On Mon, 24 Oct 2016 10:34:23 -0500, Chris Frederick wrote:
> Added Config.in options to enable/disable the option, and check options
> in sudo.mk to add openldap as a dependancy and compile with --with-ldap.
>
> When sudo is built with ldap, /etc/sudoers is only read in for defaults,
> all rules need to be provided via ldap which is configured by the user
> in /etc/ldap.conf.
>
> Since the user explicitly has to provide /etc/ldap.conf, we use 'depends
> on' so that the user is obliged to explicitly enable openldap before the
> option becomes visible.
>
> Signed-off-by: Chris Frederick <cdf123@cdf123.net>
> ---
> package/sudo/Config.in | 13 +++++++++++++
> package/sudo/sudo.mk | 7 +++++++
> 2 files changed, 20 insertions(+)
I've applied, after removing the explicit Config.in option and instead
relying on whether BR2_PACKAGE_OPENLDAP is enabled or not to decide if
ldap support should be enabled or not in sudo.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-02-06 18:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 15:34 [Buildroot] [PATCH 1/1] sudo: Add ldap support for sudoers rules Chris Frederick
2017-01-28 14:55 ` Romain Naour
2017-01-29 13:18 ` Thomas Petazzoni
2017-01-29 15:08 ` Romain Naour
2017-02-06 18:54 ` Thomas Petazzoni [this message]
2017-02-06 21:33 ` Peter Korsgaard
2017-02-06 21:38 ` Thomas Petazzoni
2017-02-06 21:52 ` Peter Korsgaard
2017-02-06 22:19 ` Chris Frederick
2017-03-02 15:36 ` Thomas Petazzoni
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=20170206195401.11ccbee3@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox