DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:from:date:message-id:subject:to
	:content-type; q=dns; s=default; b=qWWaHjt1/QrZA1OqB9dho87AIsFF4
	8fIbSvOl5NxfpmvXI6e/49TwrdHAWfP9xIpxtBersqWOJ3up7t3SfCi6d+cmdYKK
	ROVk8gr1ze0AKhl+8DZEbdjQwKwl+ToHt0ecTHjIItjAhKjBx/KAvAzq6l4EM7se
	eTwmdOJH4T3VC4=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
From: David Goldberg <dsg18096@gmail.com>
Date: Fri, 2 Aug 2019 11:45:40 -0400
Message-ID: <CAN9EdkY=zrEv31+PD8XXu9rVw4H_eXLEoMk5u=7H02Q1Xu7-Wg@mail.gmail.com>
Subject: Openldap 2.4.48-1 vs my company's pki
To: cygwin@cygwin.com
Content-Type: text/plain; charset="UTF-8"

I updated openldap from 2.4.42-1 to 2.4.48-1 this morning and now
ldapsearch will not connect, complaining that the server provided
certificate is self signed. I have set up /etc/pki with my company's
certificate chain and that allows 2.4.42-1 (and earlier) and other
applications to properly authenticate local services. What has changed in
2.4.48-1 that causes this to not work and how can I fix it. I've downgraded
for now; that is not a good long term solution of course.

Thanks,

Dave Goldberg

--
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