Bug 21077 - sudoers.ldap is using /etc/nslcd.conf, this causes nslcd to fail.
Summary: sudoers.ldap is using /etc/nslcd.conf, this causes nslcd to fail.
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: All Packagers
QA Contact:
URL: http://users.on.net/~emerson/mga/doku...
Whiteboard:
Keywords: PATCH
Depends on:
Blocks:
 
Reported: 2017-06-12 11:10 CEST by Rod Emerson
Modified: 2018-09-20 08:22 CEST (History)
1 user (show)

See Also:
Source RPM: sudo
CVE:
Status comment:

Attachments
sudo spec patch (595 bytes, patch)
2017-06-12 11:11 CEST, Rod Emerson 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Description Rod Emerson 2017-06-12 11:10:39 CEST 
Description of problem:

sudoers.ldap is using /etc/nslcd.conf, this causes nslcd to fail.

Version-Release number of selected component (if applicable):

1.8.18p1

When using /etc/nsswitch.conf "sudoers: ldap" the ldap configuration is
stored in /etc/nslcd.conf.
This causes nslcd to fail with "unknown keyword: 'SUDOERS_BASE'".

I'll attach a spec patch that changes nslcd.conf to sudo-ldap.conf
(and a fix for 21044).

References :
https://lists.arthurdejong.org/nss-pam-ldapd-users/2012/msg00234.html
https://bugzilla.redhat.com/show_bug.cgi?id=760843
Comment 1 Rod Emerson 2017-06-12 11:11:26 CEST 
Created attachment 9404 [details]
sudo spec patch
Rod Emerson 2017-06-12 11:12:16 CEST

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=21076

Rod Emerson 2017-06-12 11:13:13 CEST

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=21044

Comment 2 Marja Van Waes 2017-06-13 10:21:08 CEST 
Assigning to all packagers collectively, since there is no registered maintainer for this package.

Keywords: (none) => PATCH
CC: (none) => marja11
Assignee: bugsquad => pkg-bugs

David Walser 2017-06-18 23:53:50 CEST

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=20996

Comment 3 Marja Van Waes 2018-09-20 08:22:38 CEST 
Hi Rod,

Thank you for having taken the needed time to report this issue!

This bug was filed against Mageia 5. Did it get fixed? If so, please change its status to RESOLVED - FIXED.

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It continued to get limited extended support since then, but that support has now ended, too.
As a result we are closing this bug report as OLD.

If you still see this issue in a newer Mageia version, then please reopen this report and say so.

==> If you didn't reset your password after February 2018, then you'll need to reset it here https://identity.mageia.org/forgot_password to be able to log in and comment in this report. <==

Note that we are a community distribution, which means that we, the Mageia users, make Mageia together in our free time. If you'd like to help package & maintain sudo or any other package, then please consider becoming a Mageia packager https://wiki.mageia.org/en/Becoming_a_Mageia_Packager

Resolution: (none) => OLD
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.