Re: since update 184.108.40.206-4+deb8u5 php ldap authentification failure
On Thu, 12 Sep 2019 09:38:13 +0200 Jan Kowalsky
> Hi Mike,
> hi Hugo,
> Am 11.09.19 um 14:04 schrieb Mike Gabriel:
> > Hi Hugo,
> > sorry for the late reply on this urgent matter.
> > On So 08 Sep 2019 10:46:26 CEST, Hugo Lefeuvre wrote:
> >> Sorry for the very late answer. For some reason, it looks like the LTS
> >> team
> >> was not aware of this bug...
> >> I am the one who provided these updates. This issue must have slipped
> >> through my LDAP tests. I will investigate this as soon as possible and
> >> provide a fix consequently.
> >> Mike, you did the latest 389-ds-base update. Did you notice anything
> >> wrong
> >> during your tests?
> > For uploading 220.127.116.11-4+deb8u6, I unfortunately did not do much smoke
> > testing regarding the LDAP query stuff (the patch was about indefinite
> > SSL connection hangs).
> > Let me know, if you need help looking into this (due to e.g. time
> > constraints or what not on your side).
> as with version 18.104.22.168-2 everything worked fine, we didn't investiagte
> So I can only report that we didn't encounter any errors with all the
> versions shipped in debian 9.
I looked into this issue much deeper today and I cannot confirm the
observation this bug was originally about.
What I did:
1. Setup a fresh 389-ds instance using jessie's original version
2. Upgrade to +deb8u4, test login, LDAP queries, etc.
3. Upgrade to +deb8u5, test login, LDAP queries, etc.
4. Upgrade to +deb8u6, test login, LDAP queries, etc.
Can you be any chance provide more info about this issue? What exactly
are the LDAP queries, that Nextcloud does on your 389-ds server?
Can anyone else give feedback about 389-ds in jessie LTS? Any observed
problems that look similar to #912224 ?