Thanks,
I've now uploaded the fixed package to both unstable and bookworm-security.
The bookworm-security package needs to be processed by the security team,
so it might take a little bit longer than the version in unstable which should
be
building or already built.
Ondrej
--
Ondřej Surý
On Fri, 26 Jul 2024 14:28:12 +0200 Bernhard Schmidt
wrote:
...
>
> Can anyone confirm the workaround from the Samba BZ setting
> LDB_MODULES_DISABLE_DEEPBIND=true ?
>
>
yes, the workaround has enabled my system to work again after the
upgrade to 1:9.18.28-1~deb12u1
Ok, here's the patch:
From 6b2ffa8216bcf65f3b20b14171d9732d9583e6f7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ond=C5=99ej=20Sur=C3=BD?=
Date: Sat, 27 Jul 2024 04:57:36 +0200
Subject: [PATCH] Disable RTLD_DEEPBIND in Samba DLZ module
When RTLD_DEEPBIND is enabled in the LDB modules inside the
I think this confirms that:
https://bugzilla.samba.org/show_bug.cgi?id=15643#c6
Ondrej
--
Ondřej Surý (He/Him)
> On 26. 7. 2024, at 5:33, Bernhard Schmidt wrote:
>
> Can anyone confirm the workaround from the Samba BZ setting
> LDB_MODULES_DISABLE_DEEPBIND=true ?
There’s couple of things we can do:
- revert the jemalloc patch (it will break different scenarios though)
- compile without jemalloc (that affects memory fragmentation and performance)
- set the deep bind in the ldopen call in BIND (though I disabled it for
reason, except I can remember it now)
Processing control commands:
> found -1 9.18.28-1~deb12u1
Bug #1074378 [bind9] bind9: Bind9 SEGFAULT when enable DLZ with samba
There is no source info for the package 'bind9' at version '9.18.28-1~deb12u1'
with architecture ''
Unable to make a source version for version '9.18.28-1~deb1
6 matches
Mail list logo
