This is the mail archive of the
mailing list for the Cygwin project.
Re: Openldap 2.4.48-1 vs my company's pki
- From: David Goldberg <dsg18096 at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 6 Aug 2019 15:17:14 -0400
- Subject: Re: Openldap 2.4.48-1 vs my company's pki
- References: <CAN9EdkY=zrEv31+PD8XXu9rVw4H_eXLEoMk5u=7H02Q1Xu7-Wg@mail.gmail.com> <87ftmje5zb.fsf@Rainer.invalid> <CAN9EdkYzh558w=CG3UkzgN0rg98eVx2V0BcdktEwVEW3dS1qCQ@mail.gmail.com> <874l2y4ulo.fsf@Rainer.invalid> <CAN9EdkYG1aFnaMAPM3jg=0psRoiS1rF7Hze618UYj1mHByjKbg@mail.gmail.com> <228DE7899A9CF9C913C8B1B8@192.168.1.39> <CAN9Edkbv6ZaHyLs3MVyYapgYa3XiXU2D+kr8o2zTCJivk8h0firstname.lastname@example.org> <874l2ufdlo.fsf@Rainer.invalid>
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.
> > 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).
> +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
> SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
> 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
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple