Feature #1230

Add dynamic server blacklist

Added by Spyhawk about 1 month ago. Updated about 1 month ago.

Status:New% Done:

0%

Priority:NormalSpent time:-
Assignee:-
Category:Client
Target version:2.78
OS: Arch:

Description

I didn’t want to add such ticket till now, but that might prove to be the best course of action on the longer term.

Add a dynamic server blacklist.
We would have a small IP list downloaded at client start, that would then be used to filter out facade and other shaddy servers. The list could be downloaded from github and updated by the community through Pull Request.
This would work kinda similarly to the planned whitelist for pk3 and mod bins.

Advantage is that we could list human players count for all servers (see #1171), without the risk of seeing it exploited by shameful admins.


Related issues

Related to ET: Legacy Development - Feature #1171: Add human players count of all servers to server browser New 18.01.2019

History

#1 Updated by hellreturn about 1 month ago

Spyhawk wrote:

I didn’t want to add such ticket till now, but that might prove to be the best course of action on the longer term.

I had suggested same to Paul long time back as well in past but now i feel it’s not correct solution long term. More or less what happens when people go inactive or any of the maintainer account get hacked?

1. Be careful with the idea because I have seen someone was able to fake our server IP and show up in master list. Everything was same except port. I believe it’s same concept as getstatus DDoS. All Windows ET 3.00 from Trackbase are effected. Paul has no intention to fix it so far.

2. I believe ETL master list does the same thing ? I.e. list servers using (ETL Binaries) on top before other ET binaries. So with same logic, what those admins are doing is being done at another level by ETL team as well. You can say because of some you have to do this and that but the fact is ETL is also doing same.

3. Someone can also can run fake servers at cron job on dynamic intervals. Take SS with fake IP and blame it up on others.

4. With SOCK5 proxies available in abundant, how many IP’s will be banned? So far we have banned more then 350 subnets on our ALL servers, which consists of Class B, C and D subnets and I personally think, banning IP is not a solution.

I was against mindless blocking and deleting of pk3 files without user consent and I am against mindless blocking. I hope you can find some elegant solution.

#2 Updated by Spyhawk about 1 month ago

2. I believe ETL master list does the same thing ? I.e. list servers using (ETL Binaries) on top before other ET binaries. So with same logic, what those admins are doing is being done at another level by ETL team as well. You can say because of some you have to do this and that but the fact is ETL is also doing same.

For the record, this actually happens because of the humans player count we use. It is not inherently because of "ETL", and certainly not to give ETL binaries any advantage (we couldn’t care more about that aspect tbh). Unlike 2.76, that feature is also now semi disabled in master branch and can only be fully enabled manually by the user. See #1171 for details.

I otherwise agree with all of your points. The idea here was to manually blacklist after a thorough review of what could be considered admin abuse, but not automatically.

For full disclosure: I do find server facade completely moronic, misleading and disrepectuful towards players. They are part of what I’d personally consider "admin abuse", but not necessarily in the context of that feature (if fact we do filter the most obvious of these already). You might or might not agree here.

#3 Updated by Spyhawk about 1 month ago

  • Related to Feature #1171: Add human players count of all servers to server browser added

Also available in: Atom PDF