public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Quanah Gibson-Mount <quanah@symas.com>
To: David Goldberg <dsg18096@gmail.com>, cygwin@cygwin.com
Subject: Re: Openldap 2.4.48-1 vs my company's pki
Date: Mon, 05 Aug 2019 19:25:00 -0000	[thread overview]
Message-ID: <228DE7899A9CF9C913C8B1B8@[192.168.1.39]> (raw)
In-Reply-To: <CAN9EdkYG1aFnaMAPM3jg=0psRoiS1rF7Hze618UYj1mHByjKbg@mail.gmail.com>

--On Monday, August 05, 2019 9:22 AM -0400 David Goldberg 
<dsg18096@gmail.com> wrote:

> Sorry, was away from work over the weekend. I just tested with openssl
> s_client and it works just fine.  Version is 1.1.1.  there is no self
> signed certificate. It's signed with the company pki rather than
> commercial and I've properly installed that chain. The problem send to be
> with the new build, at least the weird ldd output leads me to that
> conclusion. I'll try to find some time to build from source and see if it

Do you mean you connected to the ldap server using OpenSSL s_client to 
confirm that works?  If that works and the ldapsearch (or other ldap 
client) binary does not, then you likely have a global /etc/ldap.conf (or 
whereever this build looks for it) or a ~/.ldaprc file that defines the 
path or file to find the CA certificate that would need updating.

Regards,
Quanah


--

Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>


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

  reply	other threads:[~2019-08-05 19:25 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 [this message]
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
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='228DE7899A9CF9C913C8B1B8@[192.168.1.39]' \
    --to=quanah@symas.com \
    --cc=cygwin@cygwin.com \
    --cc=dsg18096@gmail.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).