Nesoo: For anyone using Ubuntu 20.04 (or variations), the old version of libssl1.0.0 can be found
here.
The file can be unzipped as ChoooChooo says.
I would also do as TinMonk suggests and "install" it locally to the game. Though I would add a minor tweak on step 5, quoting the right-hand side of the expression, just to be on the safe side:
export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:./lib"
I know, the post is quite old, but here another way to solve this.
GOG has a script in
support/gog_com.shlib, which is loaded by the
start.sh script. This script has some functions to start the games in an "common" way.
The function execute_game() could be used instead of starting the binary directly. It has 6 arguments:
bin_32, bin_64 - These are the name of the binaries of the game, as 32 or 64 bit.
bin_path32, bin_path64 - Probably the directories of the binaries
lib_path32, lib_path64 - Here is the solution, the place to put extra libraries the game needs in that architecture.
So here the steps (again, but different):
1. get libcrypto.so.1.0.0 and libssl.so.1.0.0 as in the other responses
2. create the directory game/lib64 (I have a 64 bit version of the game)
3. copy the lib-Files into the game/lib64 directory
4. edit the "start.sh"-script:
4a. comment the line "
./"Mable_PC"" (put a # in the beginning)
4b. add this line after:
execute_game "" "Mable_PC" "" "." "" "lib64" 5. save the script and run the game :-)
I hope GOG will correct this.