search

Facepunch / Facepunch.Steamworks

Another fucking c# Steamworks implementation
MIT License
2.93k stars 350 forks source link

Steam Networking Sockets #413

Open unicornxiii opened 4 years ago

unicornxiii commented 4 years ago

Describe the bug Steam Networking Sockets

When connecting via ConnectP2P I get a connection error

ProblemDetectedLocally Couldn't connect End-to-end connection: closed due to problem detected locally, reason code 4003 (Bad cert: CA key is not know to us)

Failed crypto init in ConnectOK packet Bad cert

In support of Steam I was told that this

The only time we have seen this in the past, it was because steam was finding an old version of the OpenSSL libraries that had a bug in it that broke on certain Intel processors on laptops.

Does that sound likeit could be what is happening here? Can you see if somehow an old version of openssl is being loaded, and not the one we ship with Steam?

Link that describes the bug, and a potential workaround to try to confirm that it is the problem: https://software.intel.com/en-us/articles/openssl-sha-crash-bug-requires-application-update

1

If you break in the debugger and look at the modules view, you might see exactly which copy of "libeay32.dll" and "libssl32.dll" are being loaded.

(I am assuming windows here.)

garrynewman commented 4 years ago

Did you get anywhere with this? Could be a temporary problem?

nurbat commented 4 years ago

don't sent packet, debugNetwork return AckTimeout. IsConnected == true Custom packet from Connection.SendMessage return AckTimeout изображение

unicornxiii commented 4 years ago

Unfortunately no, they recommend updating OpenSSL in support (Minimum 1.0.2)

aviv0099 commented 1 year ago

@unicornxiii Did you manage to fix that issue?