Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disable client auth checks #8492

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

SirRichardFrancis
Copy link
Contributor

About The Pull Request

Basically a mirror of tgstation/tgstation#83435

Why It's Good For The Game

BYOND hub experienced technical issues recently, and players were unable to join due to that.
This change should prevent hub issues from affecting Eris.

Testing

Not possible to test currently (the hub is back online), but this compiles and runs fine.

Changelog

🆑
server: Disabled BYOND hub-based authentication.
/:cl:

@MLGTASTICa
Copy link
Contributor

i feel like this is a double-edged knife scenario , yes this will allow a bunch of people to connect when byond is having issues , but this also permits the people collecting hardware ID's and IP's (using fake servers) to join under the ACTUAL name of someone who joined any of their servers. (So if a admin joins a fake Eris and has his Hardware ID , IP and Certificate duplicated , someone could fake his ckey without authorization from byond hub with just his certificate). I suggest making this a setting that is on by default and that can be configured to be off perhaps.

@SirRichardFrancis
Copy link
Contributor Author

While there might be some security implications, I wouldn't go as far as to state theoretically possible issues as facts.

For you see, when spoofing happened in SS13 in the past, it was due to hub's own vulnerabilities, and no amount of mandatory hub verification helped.

That said, I'm not a cybersecurity guy, and this is not something I personally test. Then again, neither do you.
I'd say we do what TG does.
If they end up accepting the change, then it's probably kosher ¯\_(ツ)_/¯

@MLGTASTICa
Copy link
Contributor

MLGTASTICa commented May 25, 2024

While there might be some security implications, I wouldn't go as far as to state theoretically possible issues as facts.

For you see, when spoofing happened in SS13 in the past, it was due to hub's own vulnerabilities, and no amount of mandatory hub verification helped.

That said, I'm not a cybersecurity guy, and this is not something I personally test. Then again, neither do you. I'd say we do what TG does. If they end up accepting the change, then it's probably kosher ¯_(ツ)_/¯

Even TG mentions they don't know how secure the authentification checks are and the reason that they are doing it is because they force admins to log in through a website ontop to get acces to admin powers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants