From: David Goldberg <dsg18096@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Openldap 2.4.48-1 vs my company's pki
Date: Tue, 06 Aug 2019 21:20:00 -0000 [thread overview]
Message-ID: <CAN9Edkb2nUYmmZ76MQQN8w=PYthXctd677gxU6m3wQEgyku_yg@mail.gmail.com> (raw)
In-Reply-To: <CAN9EdkZjtczZ8hhzWTLga3iMVn+VwFOv1XNC2RZJBQUpCq+z_Q@mail.gmail.com>
I found the problem. I guess there's a number of locations where .ldaprc
can be found. I have an old backup of a Linux home directory under my
cygwin home and that contained a .ldaprc with a TLS_CACERTDIR setting that
makes no sense on my windows box. I removed it and also the ldap.conf I
just created and ldapsearch worked as expected. I can't understand why
2.4.42 ignored that file while 2.4.48 tried to use it but it seems local to
my oddball situation and not a broader issue.
Thanks again for all the help and advice.
On Tue, Aug 6, 2019, 15:17 David Goldberg <dsg18096@gmail.com> wrote:
> Thank you, Achim! I should have thought of that myself. Indeed adding an
> appropriate TLS_CACERT to ldap.conf has solved the problem and 2.4.48
> ldapsearch is working now.
>
> On Tue, Aug 6, 2019, 12:44 Achim Gratz <Stromeko@nexgo.de> wrote:
>
>> David Goldberg writes:
>> > Correct, openssl s_client works, as does the older build of
>> ldapsearch. I
>> > can't find any .ldaprc nor ldap.conf files on my system.
>>
>> Then work the other way around and create a configuration file that
>> points to the PKI. It's entirely possible that the compiled-in default
>> (if there even is one) is not correct. If so I'll have to figure out
>> how to change that, but until then it would be useful to know if things
>> start working when the config is pointing to the existing PKI (which, as
>> you tested can be used correctly by openssl).
>>
>>
>> Regards,
>> Achim.
>> --
>> +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
>>
>> SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
>> http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
>>
>> --
>> Problem reports: http://cygwin.com/problems.html
>> FAQ: http://cygwin.com/faq/
>> Documentation: http://cygwin.com/docs.html
>> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
>>
>>
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-08-06 21:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-02 15:45 David Goldberg
2019-08-02 17:28 ` Quanah Gibson-Mount
2019-08-02 19:13 ` Achim Gratz
2019-08-02 20:08 ` David Goldberg
2019-08-03 6:43 ` Achim Gratz
2019-08-05 12:22 ` David Goldberg
2019-08-05 19:25 ` Quanah Gibson-Mount
2019-08-05 19:39 ` Achim Gratz
[not found] ` <228DE7899A9CF9C913C8B1B8@192.168.1.39>
2019-08-05 20:06 ` David Goldberg
2019-08-05 20:31 ` Quanah Gibson-Mount
2019-08-05 22:41 ` Brian Inglis
2019-08-06 15:23 ` David Goldberg
2019-08-06 16:44 ` Achim Gratz
2019-08-06 19:17 ` David Goldberg
2019-08-06 21:20 ` David Goldberg [this message]
2019-08-07 18:35 ` Achim Gratz
[not found] ` <F9D491FCA6B56B38D0C0B1D6@192.168.1.39>
2019-08-03 2:42 ` David Goldberg
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='CAN9Edkb2nUYmmZ76MQQN8w=PYthXctd677gxU6m3wQEgyku_yg@mail.gmail.com' \
--to=dsg18096@gmail.com \
--cc=cygwin@cygwin.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).