search

LambdAurora / fuck_namemc

Minecraft mod to block NameMC indexing on servers.
GNU Lesser General Public License v3.0
100 stars 2 forks source link

The default configuration is broken #6

Open LambdAurora opened 2 years ago

LambdAurora commented 2 years ago

Describe the bug The default configuration does not contain the updated IP addresses of NameMC indexer.

Expected behavior NameMC being blocked on installation without any more action.

ThirdWatcher commented 2 years ago

Anyone know what the new IPs are?

LambdAurora commented 2 years ago

For anyone willing to undergo the process of finding out the new IPs:

unilock commented 1 year ago

Would you be able to upload a compiled JAR with the packet logger enabled? I'm willing to sacrifice a server of mine, but I couldn't get the JAR to compile myself. (My usual strategy of "throw everything at a wall to see what sticks" isn't quite working out.)

On that note, what would you suggest when it comes to blocking out NameMC (and similar services) these days? Is this mod still relevant? I know Fabrication has something similar now. Is there a difference between that and what Fuck NameMC accomplishes? I hope you don't mind my asking; I just think this is probably something I'd want to get right the first time...

LambdAurora commented 1 year ago

On that note, what would you suggest when it comes to blocking out NameMC (and similar services) these days?

tbh it ranges from what you have at your disposition

If it's a private server, and the people who play are only a handful of friends, I would recommend looking into wireguard as it would allow to take off the server from the world-wide Internet, avoiding any issue with NameMC and other similar services. In other cases, if you have full control of the machine/OS and it's Linux, you can look into adding REJECT iptable rules if the IPs are known.

Otherwise it's well, Fabrication obfuscating data or this. I'm quite busy lately, and I'm not sure uploading a JAR in a GitHub comment is the greatest thing :p

But the issue is, it seems that it's a game of mouse and cat, they changed IP once, nothing prevents them to switch again. I believe that the only proper long term solution is to pressure the service into providing an API to reject indexing (which shockingly isn't difficult to do because ping responses ARE JSON!!! Extra data can be added so easily!)

unilock commented 1 year ago

Gotcha. It is a private(-ish) server, but unfortunately making people jump through more hoops to connect to it wouldn't end well. I'm not exactly the most... "seasoned" server administrator.

I wonder how practical it would be to rent a server somewhere for the sole purpose of getting / exposing NameMC IPs... er, maybe that's a little overkill.

Thanks for the advice, I really appreciate it :)