Solved rsync missing libcrypto

Ome Ko

Ome Ko

Hi everyone,

openssl came along with a recent curl update. Now rsync is complaining:

Code: 
rsync: server sent "ld-elf.so.1: Shared object "libcrypto.so.11" not found.

Openssl updated 11 to 12, so libcrypto.so.12 seems to be current and libcrypto.so.11 was renamed to .111.

Did an openssl reinstall, did a rsync reinstall, set 755 on libcrypto.so.111 and made a softlink libcrypto.so.11 -> libcrypto.so.111 in /usr/local/lib, /usr/lib and /lib; nothing changed.

Any other suggestions very welcome.

PS/BTW: on one of my other servers mariadb had similar issues with libssl after the same updates, but a reinstall of mariadb fixed that.
 
Ome Ko said:
set 755 on libcrypto.so.111
Click to expand...
Libraries should not be executable. Don't do this.

Ome Ko said:
made a softlink libcrypto.so.11 -> libcrypto.so.111 in /usr/local/lib, /usr/lib and /lib;
Click to expand...
Never, ever, solve library issues this way. That's going to haunt you at a future date. Undo all of it.

What version of FreeBSD and are you using the FreeBSD packages? Or are you building your own packages/ports?
 
I'm on 13.2 & using ports. If i'm not mistaken there's a fair amount of ports handling updates with symlinks.
 
Ome Ko said:
I'm on 13.2 & using ports
Click to expand...
Did you set DEFAULT_VERSIONS+= ssl=openssl perhaps?

forums.freebsd.org

HEADS UP: security/openssl default is now openssl30

-20231014: - AFFECTS: users of security/openssl and security/openssl30 - AUTHOR: brnrd@FreeBSD.org - - The openssl port was renamed to openssl111 and subsequently the - openssl30 port was renamed to openssl. - - The shared library version of OpenSSL has been bumped. - - Users of...
forums.freebsd.org forums.freebsd.org
 
net/rsync simply uses whatever SSL has been set as default. If you didn't set DEFAULT_VERSIONS it would just link to the OpenSSL of the base.

So, what did you set in /etc/make.conf?
 
Entry in make.conf makes no difference. Installation succeeds, error message in any case the same.
Setting DEFAULT_VERSIONS+=ssl=openssl111 results in "You are using an unsupported SSL provider openssl111"
 
Regardless of whether the ports tree is up to date or not. The compilation of rsync should have aborted due to the missing library. Maybe you have one floating around in a place that is searched by the compiler/linker but not the runtime linker?
 
Removed all references to openssl12 manually, set DEFAULT_VERSIONS+=ssl=openssl and reinstalled rsync. It installed openssl as a dependency.

Seems okay for now.
 
You must log in or register to reply here.
Back
Top