From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] sudo: Add ldap support for sudoers rules
Date: Mon, 06 Feb 2017 22:52:25 +0100 [thread overview]
Message-ID: <87mvdzugva.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170206223806.5632b9ad@free-electrons.com> (Thomas Petazzoni's message of "Mon, 6 Feb 2017 22:38:06 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
> Hello,
> On Mon, 06 Feb 2017 22:33:39 +0100, Peter Korsgaard wrote:
>> > 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.
>>
>> Notice that this was discussed during the first review:
>>
>> http://lists.busybox.net/pipermail/buildroot/2016-October/175480.html
>>
>> Apparently sudo with pam support really needs a configured
>> /etc/ldap.conf, which might be confusing to people that (perhaps
>> unrelated to eachother) enabled both sudo and ldap.
> So in other words we really want to have a sub-option for this
> situation?
I don't personally know anything about it, but that was the conclusion
of Arnout and Chris, yes.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2017-02-06 21:52 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
2017-02-06 21:33 ` Peter Korsgaard
2017-02-06 21:38 ` Thomas Petazzoni
2017-02-06 21:52 ` Peter Korsgaard [this message]
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=87mvdzugva.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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