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

Add anti-abuse banning mechanisms #338

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Conversation

sxvghd
Copy link

@sxvghd sxvghd commented Mar 19, 2024

Backstory:
Few days ago I setup a public 3rd party Minecraft server for me and my friends, but some port scanning griefer found it and wrecked havoc. After setting a whitelist and installing LoginSecurity, he can no longer get in, but I can see from the logs that he's trying his hardest - constantly trying commonly used names, changing IPs and so on.
While I'm fairly happy with LoginSecurity, it doesn't seem to have any anti-abuse mechanisms, so I'm a bit worried that the guy might finally bruteforce his way in. Therefore, I decided to bite the bullet and try to implement some mechanisms myself.

This PR adds basic banning functionality in 2 flavors:

  • auto banning IPs trying to login as already active and authorized accounts
  • auto banning IPs exceeding login attempts

Both are off by default and are toggable in the config in the new ban section.
As an addition, there's another switch there too (notify-ops) which when enabled, sends a message to each server OP if a ban was to occur.
Side note, I know nothing about Java so this was written as my best approximation of "how this change really should look like", comments welcome!

Corresponding Translations PR: lenis0012/Translations#209

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.

1 participant