Hi again,
Am 17.09.19 um 18:02 schrieb Mike Gabriel:
> Hi,
> completing the story...
>
> During package upgades, I see upgrade failures:
>
> ```
> root@jessie:~# apt-get install 389-ds-base --reinstall
> Paketlisten werden gelesen... Fertig
> Abhängigkeitsbaum wird aufgebaut.
>
Hi Mike,
Am 17.09.19 um 17:38 schrieb Mike Gabriel:
> What I did:
>
> 1. Setup a fresh 389-ds instance using jessie's original version
> (see http://snapshot.debian.org/package/389-ds-base/1.3.3.5-4/)
>
> 2. Upgrade to +deb8u4, test login, LDAP queries, etc.
>
> -> worked
>
> 3. Upgrade to
Hi,
On Di 17 Sep 2019 17:38:03 CEST, Mike Gabriel wrote:
What I did:
1. Setup a fresh 389-ds instance using jessie's original version
(see http://snapshot.debian.org/package/389-ds-base/1.3.3.5-4/)
2. Upgrade to +deb8u4, test login, LDAP queries, etc.
-> worked
3. Upgrade to +deb8u5, test
Hi Jan,
On Thu, 12 Sep 2019 09:38:13 +0200 Jan Kowalsky
wrote:
> 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
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
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
Hi,
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
to mention: with version 1.3.5.17-2 in stretch everything works fine again.
Package: 389-ds
Version: 1.3.3.5-4+deb8u5
Severity: high
since 26.10.2018 our nextcloud installations can't authenticate against
389-ds anymore. This seems to have an relation to the latest update in
389-ds - it happend after we applied these two updates:
389-ds-base (1.3.3.5-4+deb8u5)
9 matches
Mail list logo