From: Filipp Gunbin <fgunbin@fastmail.fm>
To: Jens Lechtenboerger <lechten@wi.uni-muenster.de>
Cc: 58605@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#58605: 29.0.50; Commit 2a2f5530fa2 breaks ldap-search-internal
Date: Tue, 25 Oct 2022 16:12:21 +0300 [thread overview]
Message-ID: <m28rl4t5ca.fsf@fastmail.fm> (raw)
In-Reply-To: <87zgdkih0f.fsf@wi.uni-muenster.de> (Jens Lechtenboerger's message of "Tue, 25 Oct 2022 07:55:44 +0200")
Hi Jens,
On 25/10/2022 07:55 +0200, Jens Lechtenboerger wrote:
> Hi there!
>
> On 2022-10-24, Filipp Gunbin wrote:
>
>> [...]
>> But ldap-search expects ldap-ldapsearch-args to be at least what default
>> value is, to be able to parse the output (btw, "-LL" was there since
>> "forever", which is 20 years in this case; it's just the third L which
>> was added recently, to exclude ldif version from the output).
>
> How should users know about that expectation?
As I wrote, there should be no need to use it at all.
>> Also, default value can change along with ldap-search internal
>> changes. So if you want to let-bind it, you should merge in your
>> additional args, not replace them.
>
> If the code requires this, it might separate the necessary arguments
> from the customizable ones.
It does - via ldap-host-parameters-alist.
>> However, I don't see why you would want to let-bind it:
>>
>> - -H: Why don't you use host parameter?
>> - -x: just pass 'auth = simple
>> - -tt: already in ldap-ldapsearch-args
>
> When I started using LDAP, I could not make ldapsearch to use
> encrypted connections without -H. That may have changed since
> then...
Yeah, commit 0b4e003766f15225dede9bdba4ead33e493856e2 (June 2019) adds
support for LDAP URIs.
On a side note, OpenLDAP recently removed `-h' from ldapsearch
altogether.
>> Even more, I'd say that the user should set ldap-host-parameters-alist
>> according to his/her setup, and you should not mess with ldapsearch
>> arguments at all. Like:
>>
>> (setq ldap-host-parameters-alist
>> '(("ldap://example.org"
>> auth simple
>> auth-source t)))
>>
>> Then just invoke:
>>
>> (ldap-search "mail=.." "ldap://example.org" '("userCertificate"))
>
> Does this result in encrypted connections?
It should work with ldaps:// as well.
I'm now closing this issue, feel free to reopen or create new if needed.
Filipp
next prev parent reply other threads:[~2022-10-25 13:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 6:05 bug#58605: 29.0.50; Commit 2a2f5530fa2 breaks ldap-search-internal Jens Lechtenboerger
2022-10-18 14:17 ` Eli Zaretskii
2022-10-20 8:12 ` Juri Linkov
2022-10-20 17:58 ` Filipp Gunbin
2022-10-21 6:25 ` Jens Lechtenboerger
2022-10-21 15:16 ` Filipp Gunbin
2022-10-22 9:43 ` Jens Lechtenboerger
2022-10-24 16:06 ` Filipp Gunbin
2022-10-25 5:55 ` Jens Lechtenboerger
2022-10-25 13:12 ` Filipp Gunbin [this message]
2022-10-25 13:42 ` Jens Lechtenboerger
2022-10-25 15:07 ` Filipp Gunbin
2022-10-26 6:07 ` Jens Lechtenboerger
2022-10-26 13:20 ` Filipp Gunbin
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m28rl4t5ca.fsf@fastmail.fm \
--to=fgunbin@fastmail.fm \
--cc=58605@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=lechten@wi.uni-muenster.de \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).