Processing commands for cont...@bugs.debian.org:
> packsge sudo-ldap
Unknown command or malformed arguments to command.
> severity #949519 normal
Bug #949519 [sudo-ldap] sudo-ldap: Fails to connect to LDAP :
"ldap_sasl_bind_s(): Can't contact LDAP server"
Severity set to
packsge sudo-ldap
severity #949519 normal
outlook #949519 close after 2022-02-28
thanks
Lowering severity as this seems to affect just a few users.
Greetings
Marc
On Sat, Feb 20, 2021 at 08:29:05PM +0100, Dennis Filder wrote:
> Jean-Christophe, are you still interested in figuring this out? If so
> you need to provide more information. You also don't say what else
> you have tried to investigate this.
I intend to close this bug by the end of February 2022
Control: tag -1 + moreinfo unreproducible
Jean-Christophe, are you still interested in figuring this out? If so
you need to provide more information. You also don't say what else
you have tried to investigate this.
I tried reproducing your observed behaviour, but it doesn't manifest
here unless
tags 949519 + help
thanks
I do not currently have the facilities or the motivation to try and
debug LDAP issues in sudo. Happy to merge a patch if someone else
figures out what's going wrong here.
Bdale
signature.asc
Description: PGP signature
Just for information, I just run a test on a Bullseye VM with sudo-ldap
1.8.29-1 and the issue is still present in this version.
Sorry, it looks like I forget to paste the presentation of my issue on
reportbug.
I used to use sudo-ldap on Stretch to grant some rights to some users on my
servers.
I recently upgrade one of these servers to Buster, and now sudo doesn't work
anymore.
It's always the same error : "ldap_sasl_
Package: sudo-ldap
Version: 1.8.27-1+deb10u1
Severity: grave
Justification: renders package unusable
jc@server1:~$ sudo -l
sudo: LDAP Config Summary
sudo: ===
sudo: uri ldaps://server2.mydomain.com/
ldaps://server3.mydomain.com/
sudo: ldap_version 3
sudo: sudoers
8 matches
Mail list logo
