Control: tag -1 + confirmed
13.05.2022 11:33, Paul Wise wrote:
Package: samba-libs
Version: 2:4.16.1+dfsg-4
Severity: important
File: /usr/lib/x86_64-linux-gnu/libsmbldap.so.2.1.0
File: /usr/lib/x86_64-linux-gnu/samba/libads-samba4.so.0
File: /usr/lib/x86_64-linux-gnu/samba/libnet-keytab-samba4.so.0
File: /usr/lib/x86_64-linux-gnu/samba/libsamba-modules-samba4.so.0
File: /usr/lib/x86_64-linux-gnu/samba/libsmbldaphelper-samba4.so.0
The recent upgrade of samba in Debian testing made libsmbldap link
against libraries that are only in private dirs, without using a custom
library path. This means that every program that uses libsmbldap will
fail to start. It looks like not just libsmbldap has this problem
though, several of the private libraries (libsamba-modules-samba4
libsmbldaphelper-samba4 libads-samba4 libnet-keytab-samba4) also have
this issue too. It appears that other libraries in samba-libs have used
the RUNPATH option to allow finding the private samba libraries.
The commands below are how I discovered and debugged this issue.
So far there's just one such library, this is libsmbldap. All other public
libraries from samba-libs does have proper RUNPATH.
It looks like there's something in the build procedure, smells like a
missing dependency somewhere.
I filed this at important, not sure what uses those libraries.
It looks like while this lib is being put into a public library dir,
and there's a C language header for it (smbldap.h), it is still more
private library.
I'll dig into this one.
Thank you for the bugreport!
/mjt
