“Interesting”
- I have the same in my CentOS install, so I have to retract my “extremely strange” statement. And doing (only) a ln -s libcrypto.so.1.0.2k libcrypto.so.1.0.0 in /usr/lib64 (though I would still recommend ln -s libcrypto.so.10 libcrypto.so.1.0.0) does make it possible for ConfD to start, whereas without it I get the dreaded “cannot dynamically link with libcrypto shared library” error (tried with both 6.7 and 7.1).
Try with a fresh install, i.e. without rebuild from the libconfd tarball, and double-check that you got the symlink right (e.g. ls -lL libcrypto* should show the same thing for all of .so, .so.10, .so.1.0.2k, and (your symlink) .so.1.0.0)