libssl.so.1.1 issues CS2 about yolks HOT 10 CLOSED

Complain to the devs. Libssl1.1 is eol and not supported anymore for 2 +years

from yolks.

If I al allowed by the right persons. I add it back to the source and steamcmd debian one. But I can not promis anything. Its just so you all stop I'm tired of all this whining.

This should not be fixt on our side.

from yolks.

I understand what you say but sometimes its just not possible to upgrade for various reasons if the dev is not responsive for example. It would be great if there is some workarround provided from your side.

Thanks for the consideration.

from yolks.

I understand what you say but sometimes its just not possible to upgrade for various reasons if the dev is not responsive for example. It would be great if there is some workarround provided from your side.

Thanks for the consideration.

The os debian image, the source and steamcmd debian image will for now ship again with libssl1.1.

We may in the futrue just make image for games that need libssl1.1

from yolks.

Please refer to Poggicek/mysql_mm#11. Source2 games should run on debian 11 under steamrt environment, see https://github.com/1zc/CS2-Pterodactyl egg that properly does so.

Valve is trying to enforce the use of steamrt but it's still trying to be worked around causing these issues. Debian 11 still has 2 years left of support and even though libssl 1.1 is already beyond EOL it will still be patched by the debian maintainers. The developers cannot simply upgrade to libssl3 as it would completely break compatibility with debian 11 which is the only supported way to run source2 servers, at least until steamrt5 comes around which happens somewhere in 2025.

from yolks.

The siper image did not update and can be used at all time. And in about 3 weeks debian security updates. As I stated for now if you want to run the sniper image based on steam ones. Feel free to. For the time being. Libssl1.1 will still be installed on the source and steamcmd debian image.

from yolks.

okay so, the cs2 egg uses the sniper image, which is correct. What egg is then vibegames using that it does not use that image and thus does not include libssl1.1? If that's the case (vibegames using wrong egg) then no action is needed as they have clearly mentioned it occurs only for cs2 which correctly uses the steamrt3

from yolks.

THe sniper image was not touched, I am now adding back libssl1.1 to the source and steamcmd debian image.

then their now at least 4 images that have a version of libssl1.1

from yolks.

Yeah I'm not claiming that it was, the sniper image does indeed include libssl1.1 just fine, what I'm claiming is that vibegames is NOT using that sniper image for their cs2 servers for whatever reason, which is the whole reason for this to be an issue at all. I'm not exactly sure why the included "CSGO/CS2" instead of just CS2 but this issue is a result of an issue created inside my own repo which is exclusive only to CS2. So this once again loops back to vibegames' improper setup or so.

from yolks.

I am closing this, as this is some hoster issue. I thank you, @Poggicek, for your help and patient of clearing this with me.

For anyone else, there is from now libssl1.1 in the images I mentioned.
and Debian security support for 11 ends in 3 months yes the LTS team is still their.

from yolks.