Ubuntu 20.04 doesn't ship an OpenSSL 1.0 library in apt, it's moved on to OpenSSL 1.1. Is there any chance we could get a build that runs on Ubuntu 20.04? There are dependencies in the Torment/Torment64 binaries on libssl.so.1.0.0 and libcrypt.so.1.0.0. I tried to LD_PRELOAD symlinked versions in but there are compatability symbol requirements ('OPENSSL_1.0') that prevent you from using a mismatched version.

I'm sure I can go get the packages from an older Ubuntu, but grafting old OpenSSL packages into a new distro version is probably fraught.

What I did to have it working on 20.04 was indeed to copy older versions of libssl.so.1.0.0 and libcrypto.so.1.0.0 to a local folder in my /home. I then modified the startup script to add my user lib folder to my LD_LIBRARY_PATH.

It's probably fraught but it gets the job done until a proper patch is produced and I'm quite confident this won't cause any issue since I only use them for Torment.

can we just copy libssl.so.1.0.0 and libcrypto.so.1.0.0 to /usr/local/lib and add that dir into a new file in /etc/ld.conf.so.d/ and then run ldconfig??

Just a theory..... tempting to upgrade to 20.04

I'm using Debian 10 so I'm not sure if this will help you but:

sudo apt install multiarch-support
wget http://security.debian.org/debian-security/pool/updates/main/o/openssl/libssl1.0.0_1.0.1t-1+deb8u12_amd64.deb
dpkg -i ./libssl1.0.0_1.0.1t-1+deb8u12_amd64.deb

then try to launch the game. If that doesn't work try a libssl from ubuntu 16.04 that might get it to work
(http://security.ubuntu.com/ubuntu/pool/main/o/openssl/libssl1.0.0_1.0.2g-1ubuntu4.16_amd64.deb)

Thanks a million! It worked for me, with the packages from the Debian repo (I have Xubuntu 20.04).

However, there is a very good reason why that old SSL implementation is no longer available through the official repository: it is not safe! That's why I *didn't* install the package, but I unpacked it (it's an archive, I used Ark) and I just copied the required files in a "lib" directory that I created under the game's installation folder. Then, as per the instructions from this reply from another thread, I set the LD_LIBRARY_PATH, in the game's start script, to point to this lib folder and it worked like a charm.

Btw, if anyone else is having these issues and doesn't want to install an unsafe version of libssl on their system, be warned that you'll also need libcrypto.so.1.0.0. This file is also present in the libssl-1.0.0 packages above, so copy it along with libssl.so.1.0.0.

Glad it helped you, yeah I thought the ssl version might have been unsafe though I'm not sure if system applications compiled against newer versions of it would run with the old version anyway but either way your point is correct.
I'm still trying to figure out why a single player only game with no drm and no web fetching needs ssl and crypto libraries to begin with..(some left over baldur's gate multiplayer code perhaps?)

Your question was already answered, but as you mentioned it's really not the greatest idea to rampantly move binaries around to get something to link properly (this isn't windows, after all, you have source for almost everything). As long as you get the api versions correct (which latest includes OpenSSL 1.0.2X and provides OPENSSL_1.0.0-OPENSSL_1.0.2), then you can get most of the backported fixes as per the version compatibility policy at https://wiki.openssl.org/index.php/Versioning.

Anyways, If you don't want to be copying binaries around or installing rampant dependencies, I answered someone else's question here which should be the mostly correct way to solve these dependency problems especially with older shared objects as our distros completely phase out these things: https://www.gog.com/forum/planescape_torment_enhanced_edition/planescape_ee_not_working_on_my_linux_machine/post5

Hope it helps y'all, (and in the future when encountering other dep issues too).