- #How to make runes of magic private server install#
- #How to make runes of magic private server manual#
- #How to make runes of magic private server plus#
Without this, those implementations will build up the correct chain, based on "USERTrust".Ī server side workaround is to change the gameforge server and delete the outdated "Addtrust" certificate there, so the server would only send the following chain: Of course, we can't replace the wrong implementation, as this has to be done by Gameforge.Ī client side workaround for some of the wrong implementations is to delete a "Addtrust" certificate from the local certificate store. This picture (source: …Root-Expiring-May-30-2020 ) describes it very well: However, that last step is not necessary, because "USERTrust" should already be a trusted root certificate, and therefore the chain would be valid, no matter whether "Addtrust" has expired or not. However, many incorrect implementations are also trying to verify the chain further back to "Addtrust" and fail because it has expired. A correct TLS implementation which verifies the chain, should start at the end, and follow the chain until it finds a trusted root certificate, which should be "USERTrust". After that, the chain should be valid only from the end back to "USERTrust". This chain is probably sent by the gameforge servers. "Addtrust" -> "USERTrust" -> Sectigo whatever -> a certificate for Gameforge Because of this, such a certificate chain is used: But "USERTrust" was too new, and many clients did not accept it as root certificate, therefore they signed the new "USERTrust" with the old "Addtrust". The issue is, that the root certificate "Addtrust" was replaced with "USERTrust". An even better description can be found in: I have the Golem article, but never thought it could affect Runes of Magic.
So i don't know what to do next - One week without game has started((( Restarting computer and gameforge client many times didn't work Gameforge client was updating twice, all I wrote i have with last version of the client
#How to make runes of magic private server install#
The one and only option a have there - is to install the game once more. I thought 10 years is more than enough for the playing.Īnd I played all this time without "Sectigo" errors, obviously.Ĭ) " pressing "Yes" when the question pops up again" -Īfter that I'm able to log in to the Gameforge client - thats goodīut. In the end I have similar error, but now with another name and another dateĪnd as far as i understand, this new "Sectigo" error sertificate will expired in 2030. Thanks for the answer - none of this method didn't work((Ī) deleting the expired certificate + b) replacing and installing new sertificates. switch back your system time to before May 30th? XDĬ) rather simple: pressing "Yes" when the question pops up again, because this is not an attack or anything but it's simply an expired root certificate - this is just a workaround. (OpenSSL 1.0.2.X is affected, and the file has either 1.0.2.15 or 1.0.2o )ĭ) (only semi-serious). I've reported the problem and its likely issue as I'm typing this so someone who works on the Client can look into it. I suspect the libea圓2.dll from the Gameforge Client needs to be replaced with a newer version.
#How to make runes of magic private server manual#
This is probably not advisable it this section reads like Chinese to youī) …root-expired-may-30-2020/ (See the part about replacement certificates)Ĭ) rather simple: pressing "Yes" when the question pops up again, because this is not an attack or anything but it's simply an expired root certificate - this is just a workaround.Īs for a permanent solution that does not require manual fiddling by users: You can export it first via rightclick > all tasks > export, just in case. See Trusted Root Certification Authorities > Certificatesįind the "AddTrust External CA Root" and delete it. (It expired on May 30th anyway, so even if it does not fix the issue, it cant make it worse) I'm not 100% sure yet.Ī) deleting or deactivating the certificate in question on your machine. Yellow = the name of the certificate in question, so you can see its the one the google link at the top of the post is talking about.
#How to make runes of magic private server plus#
German IT news outlet : …r-aerger-2006-148840.htmlĪ closer look on the first post plus the general IT news from all over the internet point to this exact issue.Īfter 20 years(!), this root certifcate expired naturally and it is currently causing issues all over the internet because some clients rely on it.Ĭolors added to the relevant parts of the error message. Seems like some users are getting hit by the issue coming up since last weekend
0 kommentar(er)
