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.

Sign up for GitHub

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

Jump to bottom

Add a ban command #1734

Open
tornac1234 opened this issue Feb 20, 2022 · 2 comments
Open

Add a ban command #1734

tornac1234 opened this issue Feb 20, 2022 · 2 comments
Labels
Area: server moderation Related to managing server config and server player management Type: enhancement Issue is to be solved by implementing new features

Comments

@tornac1234
Copy link
Collaborator

tornac1234 commented Feb 20, 2022 •
edited
Loading

We need a ban command for the future.
@Measurity
Copy link
Collaborator

Measurity commented Feb 21, 2022 •
edited
Loading

I would start with IP bans. If it's LAN, just ignore banning because it should be easy for server owner to manage with password.

Maybe in future we can add options for more secure authentication. Like requiring a google account with payment info (without actually sending payment info to server).

We should implement this after #2006 is merged

@Jannify Jannify added the Area: netcode Related to packet serialization and networking algorithms label May 25, 2022
@Jannify Jannify added this to Nitrox May 25, 2022
@Jannify Jannify moved this to Open in Nitrox May 25, 2022
@Measurity Measurity added Type: enhancement Issue is to be solved by implementing new features Area: server moderation Related to managing server config and server player management and removed Area: netcode Related to packet serialization and networking algorithms labels Jun 12, 2022
@RokeJulianLockhart
Copy link

RokeJulianLockhart commented Oct 31, 2023 •
edited
Loading

#1734 (comment)

@Measurity, you're right, individual LAN bans are totally unenforceable – NAT makes consistent IP identification impossible, and MAC address randomization (only possible on LANs) doesn't work anymore. We'd need some pretty advanced fingerprinting to replace the venerable password.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area: server moderation Related to managing server config and server player management Type: enhancement Issue is to be solved by implementing new features
Projects
Nitrox
Status: Open
Milestone
No milestone
Development

No branches or pull requests
4 participants
@Measurity @Jannify @tornac1234 @RokeJulianLockhart