public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Openldap 2.4.48-1 vs my company's pki
Date: Fri, 02 Aug 2019 19:13:00 -0000	[thread overview]
Message-ID: <87ftmje5zb.fsf@Rainer.invalid> (raw)
In-Reply-To: <CAN9EdkY=zrEv31+PD8XXu9rVw4H_eXLEoMk5u=7H02Q1Xu7-Wg@mail.gmail.com>	(David Goldberg's message of "Fri, 2 Aug 2019 11:45:40 -0400")

David Goldberg writes:
> 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.

The PKI layout was slightly changed a while ago and the newer openssl
library used by the fresh openldap build may not pick up on the old
locations anymore.  What you should do is place the certificates into
the /etc/pki/ca-trust/source/anchors/ directory, then run

# update-ca-trust extract

which should correctly populate the directories that the libaries and
applications use.



Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves

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

  parent reply	other threads:[~2019-08-02 19:13 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 [this message]
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
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=87ftmje5zb.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).