Re: (ITS#9014) OpenLDAP modifies user provided TLS certificate before sending it to client

2019-04-24 Thread siddjain
--_000_MWHPR08MB2400D7AE5E8EEC3D17192FACB53C0MWHPR08MB2400namp_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Thank you. we tried using another openldap image and that worked. so it see= ms the problem is with the osixia docker image we were using to

Re: (ITS#9014) OpenLDAP modifies user provided TLS certificate before sending it to client

2019-04-24 Thread quanah
--On Wednesday, April 24, 2019 6:43 PM + h...@symas.com wrote: > siddj...@live.com wrote: >> --_000_MWHPR08MB24000D77048AFCF7465C4397B53C0MWHPR08MB2400namp_ >> Content-Type: text/plain; charset="iso-8859-1" >> Content-Transfer-Encoding: quoted-printable >> >> could you send me output of

Re: (ITS#9014) OpenLDAP modifies user provided TLS certificate before sending it to client

2019-04-24 Thread hyc
siddj...@live.com wrote: > --_000_MWHPR08MB24000D77048AFCF7465C4397B53C0MWHPR08MB2400namp_ > Content-Type: text/plain; charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable > > could you send me output of running > > openssl version -a > > on your system? thanks > openssl version

Re: (ITS#9014) OpenLDAP modifies user provided TLS certificate before sending it to client

2019-04-24 Thread siddjain
--_000_MWHPR08MB24000D77048AFCF7465C4397B53C0MWHPR08MB2400namp_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable could you send me output of running openssl version -a on your system? thanks From: Howard Chu Sent:

Re: (ITS#9014) OpenLDAP modifies user provided TLS certificate before sending it to client

2019-04-24 Thread hyc
Siddharth Jain wrote: > Wow! Thanks for responding so fast. This could be a bug in docker-openl= dap then. we have repro'ed this in two different environments - mac and u= buntu. Do you > have a recommendation for docker image for openldap? As I said before, OpenLDAP doesn't touch the certificate

Re: (ITS#9014) OpenLDAP modifies user provided TLS certificate before sending it to client

2019-04-24 Thread siddjain
--_000_MWHPR08MB2400F5334463D5A204E8CF88B53C0MWHPR08MB2400namp_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Wow! Thanks for responding so fast. This could be a bug in docker-openldap = then. we have repro'ed this in two different environments - mac

Re: (ITS#9014) OpenLDAP modifies user provided TLS certificate before sending it to client

2019-04-24 Thread hyc
Siddharth Jain wrote: > we have documented complete steps to repro the bug=A0here =A0with container logs. I see no error here. Using your cert/key files: > ls -l /tmp/jnj total 12 -rw-r--r-- 1 hyc hyc 1592 Apr 24 17:34 jnj-ca-chain.pem -rw-r--r-- 1

Re: (ITS#9014) OpenLDAP modifies user provided TLS certificate before sending it to client

2019-04-24 Thread siddjain
--_000_MWHPR08MB24001BB2C0F56927A628AF69B53C0MWHPR08MB2400namp_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable we have documented complete steps to repro the bug here with container logs.

Re: (ITS#9015) Replication goes haywire querying promoted master

2019-04-24 Thread ondra
On Tue, Apr 23, 2019 at 11:28:40PM +, qua...@symas.com wrote: > --On Tuesday, April 23, 2019 8:56 PM +0200 Ond=C5=99ej Kuzn=C3=ADk=20 > wrote: >> Going by what I think I remember of the consumer code did: >> - on set up, it finds out there's no cookie to go by so it goes into >> refresh on

Re: (ITS#9016) cn=config should fail on EMIT if target directory not empty

2019-04-24 Thread michael
This is a cryptographically signed message in MIME format. --ms030705030102060301060203 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 4/24/19 1:32 PM, on...@openldap.org wrote: > Since it's not feasible to clean up

(ITS#9016) cn=config should fail on EMIT if target directory not empty

2019-04-24 Thread ondra
Full_Name: Ondrej Kuznik Version: re24/master OS: URL: Submission from: (NULL) (82.10.24.68) Running slapd/slaptest to convert a slapd.conf to cn=config will happily reuse the target directory. However if there was some existing configuration present already, slaptest reports a successful