Yes. It works 😊
вт, 22 окт. 2019 г., 13:59 Jonathan Matthew <jonathan@d14n.org>:
> On Tue, Oct 08, 2019 at 09:44:52AM +0200, Jeremie Courreges-Anglas wrote:
> > On Mon, Oct 07 2019, "dmitry.sensei" <dmitry.sensei@gmail.com> wrote:
> > > No problem 👍
> > >
> > > пн, 7 окт. 2019 г., 16:17 Klemens Nanni <kn@openbsd.org>:
> > >
> > >> jca@ sent an update to samba 4.9.x along its request for testing to
> > >> ports@ on 04.10.2019, can you check whether the new version still has
> > >> this problem?
> >
> > I did not try to reproduce, mostly because I don't have any DC setup to
> > test with. The AD DC code has always been brittle on OpenBSD (we have
> > no ACLs or extended attrs support); I don't recommend it for
> > "production" use, and I might disable it in the next updates if it's in
> > the way.
> >
> > I haven't tried to look at the code to see if there's an obvious reason
> > for this segfault. Maybe in the next days, as time permits.
> > A backtrace with the samba-4.9.13 package would be welcome. Bonus
> > points if you rebuild databases/openldap with DEBUG=-g. :)
>
> I ran into this today and found an annoyingly obvious cause. 'net' picks
> up
> ber_free() from libutil, which is definitely not the same as ber_free()
> from
> liblber. LD_PRELOAD=/usr/local/lib/liblber.so.x.y makes it work better.
> The last time I joined samba on an OpenBSD host to an AD domain, it was on
> 6.5,
> where the ber code wasn't in libutil.
>
>
No comments:
Post a Comment