It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Community
Baldur's Gate seriesLinux: Baldur's Gate Enhanced Edition uses old SSL libs(15 posts)(15 posts)
(15 posts)
Pages:
1
This is my favourite topic
Posted October 11, 2021
I just installed Baldur's Gate: Enhanced Edition on my Slackware64-current Linux box.
Upon starting the game I was greeted with these messages:

./BaldursGate: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory

This message appeared first for libssl.so.1.0.0 and then for libcrypto.so.1.0.0.

The thing is that these libs belong to OpenSSL 1.0, which is ancient. Slackware switched to OpenSSL 1.1. on 2013 and now these lib versions are strongly deprecated and their presence in a system is right now, I think, a security risk.

I had to hunt an old openssl-solibs package to extract these ancient libs. Once they were somewhere in my $PATH, the game ran fine.

Dear GOG: Can you please update the build so we can run it with OpenSSL libs version 1.1? Thanks in advance.
Posted October 11, 2021
I have the same problem on fedora 34. Installed BG1EE with minigalaxy and when I try to start the game I get:

Running Baldur's Gate: Enhanced Edition
./BaldursGate: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory

I tried looking for a solution online but to no avail :( my linux knowledge is pretty limited and I don't really know what to do.

I guess I have to retrieve libssl-1.0.0 online and then edit the start.sh script to let the game load them, but it's way too complicated for me. Why beamdog don't update those libraries to a newer version?
Post edited October 12, 2021 by c1cc1099
Posted October 11, 2021
low rated
yawn.

on another note what does warrant raising this 390845093485th time - why the heck beamdawgs won't get rid of the dependency entirely
Posted October 11, 2021
avatar
thegreyshadow: Dear GOG: Can you please update the build so we can run it with OpenSSL libs version 1.1?
This forum is not a good venue for alerting GOG to problems with the packaging of the game. You should open a ticket with GOG Support about the issue.
avatar
c1cc1099: I tried looking for a solution online but to no avail :( my linux knowledge is pretty limited and I don't really know what to do.

I guess I have to retrieve libssl-1.0.0 online and then edit the start.sh script to let the game load them, but it's way to complicated for me.
The original poster described this in brief. I agree that it is more complicated than it should be. In my opinion, the game should work after installation, without requiring you to make this change.
avatar
c1cc1099: Why beamdog don't update those libraries to a newer version?
That would be best addressed to a Beamdog spokesperson. I don't think any of them are regulars here.

For both of you - an alternative workaround is to use Wine to run the Windows version of the game.
Posted October 11, 2021
low rated
*spokesman

spokesperson is dumb and cringe

dont @ me
Posted October 11, 2021
avatar
osm: yawn.

on another note what does warrant raising this 390845093485th time - why the heck beamdawgs won't get rid of the dependency entirely
Two things:

1. Sorry for the noise if this is repeat. Searched the forum and got no significant hits on this issue.

2. Indeed, why does BG1EE need SSL??
Posted October 12, 2021
avatar
advowson: That would be best addressed to a Beamdog spokesperson. I don't think any of them are regulars here.
A support ticket was rasied to GOG support. Anyway, I wanted to alert fellow Linuix gamers about this too, so I wrote this topic.
avatar
advowson: For both of you - an alternative workaround is to use Wine to run the Windows version of the game.
No. That would imply the added complexity of a gigabyte-sized software package, and prior to that, the hassle of maintaining a multilib setup, as required by Wine (my system is pure 64-bit).

I'd rather install the game on my Windows partition and play from there if I have to use the Windows version.
But I think a fix for this is trivial (just a rebuild) when one has access to the source code, so I think requesting a fix is appropriate.
Posted October 12, 2021
avatar
advowson: That would be best addressed to a Beamdog spokesperson. I don't think any of them are regulars here.
avatar
thegreyshadow: A support ticket was rasied to GOG support. Anyway, I wanted to alert fellow Linuix gamers about this too, so I wrote this topic.
You really ought to let the developer know rather than the storefront. They are different people entirely.
Posted October 12, 2021
low rated
avatar
advowson: For both of you - an alternative workaround is to use Wine to run the Windows version of the game.
for both of them would be of great benefit if the mods actually did their work and cleaned the threads up from idiots and their outrageously misguided 'advice' (I'd repped if it was some ingenious trolling, but alas...)

rather than go all out on CoC hunting
Post edited October 12, 2021 by osm
Posted October 12, 2021
avatar
advowson: For both of you - an alternative workaround is to use Wine to run the Windows version of the game.
avatar
thegreyshadow: No. That would imply the added complexity of a gigabyte-sized software package, and prior to that, the hassle of maintaining a multilib setup, as required by Wine (my system is pure 64-bit).
The current releases of the game for Windows are 64-bit. They should be usable with a 64-bit-only Wine.
avatar
thegreyshadow: But I think a fix for this is trivial (just a rebuild) when one has access to the source code, so I think requesting a fix is appropriate.
OpenSSL version bumps are not necessarily trivial. However, considering how many years overdue a bump is, I agree that requesting a fix is appropriate.
Posted January 25, 2024
I've managed to build and embed the ssl and crypto libs into the BGEE game folder so you don't need to replace the system wide SSL with an insecure old version.
I'm using Elementary OS 7.1 but its based off Ubuntu 22.04 so these instructions should work on Ubuntu 22.04 and possibly newer versions.

Prerequisites
You will need some experience with using the terminal in linux.
You will need to be able to compile the OpenSSL package so you will need gcc installed as well as few other tools.
On ubuntu this can be done with the following command:
sudo apt install build-essentials

Compiling OpenSSL
Once you have your build tools installed you can download and compile OpenSSL.
The version you need is 1.0.1u which you can download from the OpenSSL website www.openssl.org/source/old/1.0.1/index.html
Once downloaded you will need to unpack the source code to compile it:
tar -zxvf ~/Downloads/openssl-1.0.1u.tar.gz

This will create a openssl-1.0.1u folder. You can then change directory into this folder by using this command:
cd openssl-1.0.1u.tar

Now we can begin to configure and compile the openssl code:
./Configure shared linux-x86_64
make

This will run for some time and should hopefully complete successfully.
You'll know if its completed successfully if the following command:
ls *.so.1.0.0

returns:
libcrypto.so.1.0.0 libssl.so.1.0.0

Configuring BGEE
Now we can copy these files to the BGEE game folder and configure it to make use of them.
To copy them to the correct folder use this command changing the PathToBGEE to the correct path
cp *.so.1.0.0 PathToBGEE/game

Now we need update the start script to make use of these libraries.
In your BGEE game folder there is a file called start.sh. Opening this in a text editor will allow you to change a line to make the game use the newly compiled libaries.

In the start.sh change the line
./"BaldursGate"
to
LD_LIBRARY_PATH=`pwd` ./"BaldursGate"

Now you should be able to launch and play the game.
Posted January 28, 2024
avatar
SuperRad.406: I've managed to build and embed the ssl and crypto libs into the BGEE game folder so you don't need to replace the system wide SSL with an insecure old version.
I'm using Elementary OS 7.1 but its based off Ubuntu 22.04 so these instructions should work on Ubuntu 22.04 and possibly newer versions.

Prerequisites
You will need some experience with using the terminal in linux.
You will need to be able to compile the OpenSSL package so you will need gcc installed as well as few other tools.
On ubuntu this can be done with the following command:
sudo apt install build-essentials

Compiling OpenSSL
Once you have your build tools installed you can download and compile OpenSSL.
The version you need is 1.0.1u which you can download from the OpenSSL website www.openssl.org/source/old/1.0.1/index.html
Once downloaded you will need to unpack the source code to compile it:
tar -zxvf ~/Downloads/openssl-1.0.1u.tar.gz

This will create a openssl-1.0.1u folder. You can then change directory into this folder by using this command:
cd openssl-1.0.1u.tar

Now we can begin to configure and compile the openssl code:
./Configure shared linux-x86_64
make

This will run for some time and should hopefully complete successfully.
You'll know if its completed successfully if the following command:
ls *.so.1.0.0

returns:
libcrypto.so.1.0.0 libssl.so.1.0.0

Configuring BGEE
Now we can copy these files to the BGEE game folder and configure it to make use of them.
To copy them to the correct folder use this command changing the PathToBGEE to the correct path
cp *.so.1.0.0 PathToBGEE/game

Now we need update the start script to make use of these libraries.
In your BGEE game folder there is a file called start.sh. Opening this in a text editor will allow you to change a line to make the game use the newly compiled libaries.

In the start.sh change the line
./"BaldursGate"
to
LD_LIBRARY_PATH=`pwd` ./"BaldursGate"

Now you should be able to launch and play the game.
gawd
Posted March 06, 2024
avatar
SuperRad.406: I've managed to build and embed the ssl and crypto libs into the BGEE game folder so you don't need to replace the system wide SSL with an insecure old version.
Good stuff, thanks!

Edit: I managed to get it running by simply doing the LD_LIBRARY_PATH=`pwd` ./"BaldursGate" renaming and then copying over all missing libraries (as determined by the terminal output when trying to run the start.sh) with those provided by my STEAM installation in home/USER/.steam/debian-installation/ubuntu12_32/steam-runtime/lib/x86_64-linux-gnu

No need to compile anything!
Post edited March 06, 2024 by FarTooNice
Posted March 06, 2024
avatar
FarTooNice: I managed to get it running by simply doing the LD_LIBRARY_PATH=`pwd` ./"BaldursGate"
No need to compile anything!
AMAZING!!11 You're not one of those... eh.. hackers right? If you are you could be dangerous.

PS BTW no need for pwd either.

PPS might want to read up on ld.so.conf.d which is the "official" way these days for this sorta thing, but IMO it's an overkill for a case like this. Guess it depends what you are lazier to do - put a file in /etc/... or stick the env var somewhere.
Post edited March 08, 2024 by osm
Posted March 25, 2024
I came here to check this. I've got the same with PLS EE and BGEE II (which I end up buying from Steam) I'm not taking chances any longer.
Pages:
1
This is my favourite topic
Community
Baldur's Gate seriesLinux: Baldur's Gate Enhanced Edition uses old SSL libs(15 posts)(15 posts)
(15 posts)