I did some research, and it looks like adcli fires the same linker
warnings I was seeing, but just ignores them and everything works. I
guess I will have to go down the path of dynamically checking
dependencies for the LDAP package at runtime and only load the library
if it doesn't conflict, meanin
>As far as I know the libldap packages in those distros don't directly
>link a GSSAPI library at all. Ubuntu is the only one I'm aware of that
>enables this.
Yes. On other distros, it links directly to libkrb5.so. That in turn can
either link to Heimdal or MIT, resolving the problem.
I will look
Ryan,
That makes sense. And yes, if I could deal with credentials like LDAP
does, that would be incredibly convenient, but I cannot.
In theory, I can parse the ELF structure of the LDAP library at runtime,
check if there is the dependency issue, and then load the ldap library
dynamically if every
Ryan,
The dependency is a problem because my program depends on gssapi_krb5,
krb5, sasl, and openldap. On Ubuntu, the linker will throw errors
because "libkrb5.so.26, needed by //usr/lib/x86_64-linux-
gnu/libgssapi.so.3, may conflict with libkrb5.so." libgssapi.so.3 is
required by libldap2-dev as
Ryan,
Ah, MIT vs Heimdal implementations make sense. Is there a way to install
openldap with a dependency on MIT kerberos instead of Heimdal? From the
dependencies listed at https://packages.ubuntu.com/trusty/libldap-2.4-2,
it looks like the default openldap package depends on Heimdal. Also, is
th
Public bug reported:
Currently, Ubuntu 16.04's newest offered version of OpenLDAP is version
2.4.42. This version depends on libgssapi3 which in turn depends libkrb5
version 2.6. Many other common libraries (like gssapi_krb5) depend on
libkrb5 3.0. From what I can tell, OpenLDAP version 2.4.44 fix
