Problems with openssl libraries & multiplayer (Linux)

[Fincer]

Hey,

I'm using Arch Linux. I've installed the latest Zandronum Development version (Zandronum 3.0-alpha-151228-1140, 64-bit). Every time I launch either Zandronum or Zandronum server, I get the following message:

Code: Select all

[fincer@fincer-laptop zandronum]$ zandronum
/usr/share/zandronum/zandronum: /usr/lib/libcrypto.so.1.0.0: no version information available (required by /usr/share/zandronum/zandronum)
...
...
...

This is not an issue with single player games but problems arise when trying to play in multiplayer (Doomseeker). Zandronum says in Doom console that "Protected Lump Authentication Failed" and gives shasums of all used files, no matter how many times me and my friend check the loaded files. The authentication problem is very likely related to OpenSSL since Windows version with exactly the same files works without any issues, and I can join my friend's server, too. Linux version fails, always. Fails, fails, fails.

I have no idea what to do. I have openssl-1.0.2.e installed on my system. However, I tried various other versions, too (1.0.2.d, 1.0.2.a, 1.0.2, 1.0.1.i, 1.0.1.h, 1.0.1.g) and got always the same message: "no version information available".

Could someone help me figure out this issue? It gets really painful. What specific OpenSSL version do you guys use in precompiled Zandronum 3.0 packages? What can I do? What does cause this issue?

Any help is appreciated.

[Dusk]

Protected lump authentication has nothing to do with OpenSSL. Your files are different and you're just missing something. The error message does not list the IWAD so I'd check whether there's a problem with that.

And please don't tell me that you stuffed brutal doom into the skins folder...

[Fincer]

Well, this is what I get on Linux while trying to connect to a server (you can check shasums yourself):



Exactly same files, exactly same configuration. Same program versions. Works on Windows, no problems. And yes, we both use same Doom2.wad IWAD, either Linux or Windows.

You may then explain what causes this issue? I have, identical files, compared to the files my friend has on his computer. And yes, this is an old issue, because this has happened on earlier Zandronum 3.0 builds, too. If it's not OpenSSL, can it be some other library instead?

Singleplayer works.

-----------------------------------------

P.S. Okay, we investigated this little bit further. Problem solved, as what comes to Zandronum.

this is somehow related to Project Brutality wads. Not sure how and why, but once we unloaded all PWADs, Zandronum worked without issues in multiplayer.

Case closed.

[Konar6]

Does the wad name have spaces in it?

[Fincer]

Nah, sorry this is confusing but...we tested this again, I'm sure now. Just forget all what I've said above. Let's clear the table at once.

If I run Windows version of Zandronum via Wine and my friend uses Windows version as well, we have no problems with custom WADs. I'm now quite sure this is an issue either between Linux & Windows Zandronum versions (binary conflict?) or some naming issue of the custom WAD files, therefore possibly nothing related to Project Brutality. We tried renaming all custom WADs with lower case letters as well, no success. Same error. This issue is relevant only when using custom WADs (Project Brutality at least).

WADs don't have spaces in their names. Actually it doesn't matter whether custom files have spaces or not since we've tested it.

My conclusion is as follows

Windows Zandronum 3.0 + Windows Zandronum 3.0 = works with custom WADs and with a basic iWAD only (such as doom2.wad)
Windows Zandronum 3.0 + Linux Zandronum 3.0 = doesn't work with custom WADs but works with a basic iWAD only (such as doom2.wad)
Linux Zandronum 3.0 + Linux Zandronum 3.0 =

Hopefully this get's fixed...somehow... since it's quite annoying. I can't use my native Linux Zandronum in multiplayer mode. That's why I'm forced to use Wine to run it instead for the time being.

[Torr Samaho]

We have been mixing Windows and Linux binaries for years, so this shouldn't be a general problem. Can you post the part of the console logs of both client and server that starts with "W_Init: Init WADfiles."?

[RunFish]

Well, this is what I get on Linux while trying to connect to a server (you can check shasums yourself):

Chances of you seeing this are slim, but I'm having the same issue. I don't really understand what your fix was. Anyone else able to shed some light on this?

[WaTaKiD]

https://zandronum.com/forum/viewtopic.p ... 418#p99413

https://zandronum.com/tracker/view.php?id=2775