Our dedicated server clients have the ability to host sessions, so they can advertise themselves publicly on the server browser. These dedicated server clients are distributed publicly, and are run and managed by the player community.
However some players are abusing the ability to host sessions by sending EOS a bunch of requests to create fake sessions.
By extracting our dedicated server’s client ID and secret, they are able to write a script that authenticates itself as a dedicated server, and then the script will send HTTP requests to EOS in order to host multiple sessions. This floods the server browser with fake or duplicate server listings. We are able to catch some of these sessions and filter them out via our client, but if enough fake sessions are present, they can crowd out legit server sessions, due to the maximum server limit of EOS query responses.
Is there a way we could limit or verify a client’s ability to host sessions? For example setting a limit of 1 session per IP. Perhaps a way to run a verification script before accepting the client’s request? Or some way to prune sessions that don’t correspond to a legit server? If none of that is possible, what would you recommend?
Would it be feasible to explore separating community servers into a separate EOS product to separate the community sessions from official ones?
With this setup, you can provide the community with client credentials that do not allow them to create deployments in your official deployments.
This would impact how you need to initialize the SDK, using separate credentials and identifiers for each pool of servers.
To aid with this, you should be able to run two instances of the EOS_Platform simultaneously, though we would suggest thorough testing and using separate threads to manage these.
Unfortunately I don’t think that would work for us, as the vast majority of our servers are community hosted.
I understand that the problem is that we are publicly distributing a client that has permissions to create sessions. And there is nothing between the client and EOS that can handle validation or rate limiting.
So is our only solution to remove the client’s ability to create sessions? We can explore that option but it would be the last choice for us. Any other levers we can pull before that?