On (14/01/20 13:33), Sad Clouds wrote:
>Hi Lukas, as far as I can see, /sbin/sssd binary does not depend on libldap at 
>all. If you run "ldd -v /sbin/sssd" it will show you which libraries pull in 
>libnss3:
>

I have no idea how did you build and copy/install sssd yourself on CentOS & but
I cannot reproduce it.

I used the same configure paramets as you + standard make way to isntall
binaries

./configure --prefix=/usr --libdir=/usr/lib64 --sysconfdir=/etc
  --localstatedir=/var --with-crypto=libcrypto --enable-nsslibdir=/lib64
  --enable-pammoddir=/lib64/security --disable-krb5-locator-plugin
  --disable-cifs-idmap-plugin --without-nfsv4-idmapd-plugin
  --disable-pac-responder --disable-nls --without-python2-bindings
  --without-python3-bindings --without-autofs --without-samba --without-kcm
  --without-selinux --without-semanage --without-manpages --without-libwbclient
&& make && sudo make install

[root@host sssd-2.2.4]# ldd /usr/lib64/sssd/ | grep nss
conf/                  libsss_cert.la         libsss_crypt.so        
libsss_iface.la        libsss_krb5.so         libsss_ldap_common.la  
libsss_sbus.so         libsss_simple.la
libifp_iface.la        libsss_cert.so         libsss_debug.la        
libsss_iface.so        libsss_krb5_common.la  libsss_ldap_common.so  
libsss_sbus_sync.la    libsss_simple.so
libifp_iface.so        libsss_child.la        libsss_debug.so        
libsss_iface_sync.la   libsss_krb5_common.so  libsss_proxy.la        
libsss_sbus_sync.so    libsss_util.la
libifp_iface_sync.la   libsss_child.so        libsss_files.la        
libsss_iface_sync.so   libsss_ldap.la         libsss_proxy.so        
libsss_semanage.la     libsss_util.so
libifp_iface_sync.so   libsss_crypt.la        libsss_files.so        
libsss_krb5.la         libsss_ldap.so         libsss_sbus.la         
libsss_semanage.so     modules/
[root@host sssd-2.2.4]# ldd /usr/lib64/sssd/libsss_ldap_common.so | grep nss
        libnss3.so => /lib64/libnss3.so (0x00007f037e3d6000)
        libnssutil3.so => /lib64/libnssutil3.so (0x00007f037e1a6000)
[root@host sssd-2.2.4]# objdump -p  /usr/lib64/sssd/libsss_ldap_common.so | 
grep NEED
  NEEDED               liblber-2.4.so.2
  NEEDED               libldap-2.4.so.2
  NEEDED               libsss_krb5_common.so
  NEEDED               libkeyutils.so.1
  NEEDED               libkrb5.so.3
  NEEDED               libk5crypto.so.3
  NEEDED               libcom_err.so.2
  NEEDED               libsss_idmap.so.0
  NEEDED               libsss_util.so
  NEEDED               librt.so.1
  NEEDED               libpopt.so.0
  NEEDED               libldb.so.1
  NEEDED               libdbus-1.so.3
  NEEDED               libtdb.so.1
  NEEDED               libglib-2.0.so.0
  NEEDED               libpcre.so.1
  NEEDED               libini_config.so.3
  NEEDED               libbasicobjects.so.0
  NEEDED               libref_array.so.1
  NEEDED               libcollection.so.2
  NEEDED               libsss_cert.so
  NEEDED               libsss_certmap.so.0
  NEEDED               libsss_crypt.so
  NEEDED               libcrypto.so.10
  NEEDED               libsss_child.so
  NEEDED               libtevent.so.0
  NEEDED               libtalloc.so.2
  NEEDED               libdhash.so.1
  NEEDED               libsss_debug.so
  NEEDED               libdl.so.2
  NEEDED               libc.so.6
  VERNEED              0x0000000000008968
  VERNEEDNUM           0x0000000000000008
[root@host sssd-2.2.4]# objdump -p  /usr/lib64/sssd/libsss_ldap_common.so | 
grep NSS
[root@host sssd-2.2.4]#


and /usr/lib64/sssd/libsss_ldap_common.so  is still indirectly linked with NSS 
crypto due to libldap-2.4.so.2 :=)

HTH

BTW I had bot nss and openssl headers installed on the system

LS
_______________________________________________
sssd-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/[email protected]

Reply via email to