AntiMulti
This is AntiMulti. It is a plugin designed to prevent the use of alternate accounts from the same IP address. To put it simply, a player cannot use multiple accounts on the same IP address and likewise, will not be able to use a ton of IPs.
Download: Download
AntiMulti is a plugin which has undergone multiple changes from its original intent to be a simple plugin to prevent alternate accounts from being used on a server by blocking too many accounts from sharing an IP to a plugin which can also prevent session stealing using this same concept and also supporting admin protection. This is done simply by using an IP system to prevent the unauthorized use of an account by using IPs to prevent session stealing from working in the first place. All of this is completely toggle-able in the configuration file in case one does not use want to use certain features or not.
There are a few things you must understand when using this plugin. This is not a one-hit wonder in that it can stop all alternate accounts, as proxies would be able to get around this system, however common proxies would eventually be blocked after they are used enough. This does its best though to stop a member from simply using 2 accounts to gain an advantage over another player.
There are 2 groups this plugin will understand: Players and Admins. Players are normal players and are not forced to use the protection system as strictly as admins. Players are more loosely held initially by allowing more connections per name and IP, however this can be changed. Admins are more protected to prevent the taking of the account to cause problems by forcing registration and using a smaller range of names and IPs that can those accounts can share. This is all permission based in that there is a perm that designates whether the player is an admin or a player, which is just antimulti.admin, which if given, marks the player as an admin and handles them accordingly.
We do have Metrics with this plugin, so stats will be sent to our mcstats page if you are opt-ed in, where that config is located in the PluginMetrics folder.
If you have any issues, please create a ticket here with the log file and as much information as you can provide so the issue can be investigated and handled. If you have a question, feel free to ask here but please read everything first before you ask since your question may have already been answered elsewhere.
UPDATE: I have released 2.0.3, which has a new update system with a small warn to the recommendation of any updates. Also have added back in the login system and patched the add command to allow for case-insensitivity. Also, IPs can be defined now with wildcards, so 192.168.1.* is acceptable but only will count as 1 IP. This has to be added manually using either the add command or editing the files.
@brickh
Just read the rest of the reply.
The whitelist feature is permission based, so users and groups can be added by just giving the correct permissions. I did override the vanilla whitelist since i thought it would be worth it to just use this one as it is just an improved whitelist, but I can look into a config setting where /whitelist can activate the vanilla whitelist and one of the aliases for the whitelist (amwhitelist, amwl) can use mine.
@brickh
Yeah, I just noticed that the names did have to be case-sensistive. I am going to fix that in the next version to avoid this kind of issue. The file will have priority over the settings, so if they are in the file, it will let them in regardless if the limit is reached, all it does is just not add any more.
@Lord_Ralex
Hey there,
So it appears that I may have made a mistake - everything seems to be working fine. When I added the names to the IP.yml I didn't realize they had to be case-sensitive. I can easily try this, but just to ask without experimenting, am I able to keep the max-names to 1 and edit the IP.yml to have three names? I just didn't know if that setting truncated the list after the first name or if it only allows the mod to write one name per IP.
To comment on the whitelist feature - is it strictly for whitelisting groups? Unfortunately, it interferes with the ability to use the in-game whitelist command. Would it be OK to suggest altering the command in the next release?
@Milestailsprower1337
Because of the way this works, when set up, the admins can in fact be protected from session stealing since this uses IPs to verify a player. This means that if you only allow 1 ip per admin, then the ip they first use will be the only IP they can use. Session stealing cannot get by that. As such, it is a very good way to protect from that.
By it does not deactivate, does it not show a message saying it was deactivated or that it says it does deactive but it still blocks people?
Also, being curious, what was the thread on mcf that led you here?
me and my friend got sessionstealer used on us now in a minecraft fourms post someone linked me to this and said it would stop session stealer is that true and also when i deactivate the antimulti whitelist it is not really deactivated help?
@brickh
I am not close to internet locations, but I will see what is going on and get back to you as soon as I can. I thought the files should have let them in, but I will look at the coding and see what is happening, and get some sort of debug system so that in the future it is easier to see what is happening.
Yes, when I upgraded from 1.9.1 to 2.0.2, I let it regenerate an entire new folder.
This is the default config it creates:
logins-per-second: 5
max-ips: 2
max-admin-ips: 1
max-names: 1
max-admin-names: 1
and then a folder called userData with a name.yml and ip.yml for each player.
In the pastebin below, I pasted the contents of the three players' .yml's and the one ip.yml that the three players are using.
@brickh
I believe i changed the config in 2.0.2 to a more cleaner system. Have you tried letting it remake it?
config.yml for AntiMulti: logins-per-second: 5 max-ips: 1 max-admin-ips: 1 max-names: 3 max-admin-names: 1
Here are the four files involving the three players in question: http://pastebin.com/58WaGAeX
The names were edited in while max-names was still 1, assuming we could edit the files for the specific players instead of raising the limit for all players. After that didn't work, we increased the number to 3 in case it was truncating the list. I'm almost certain that was the series of events that occurred.
I believe we also deleted all the player files and tried to allow the mod to re-create them with max-names set to 3 but it still wouldn't let the other two players in (Kelebrae and MrXenos). pr1v4t3 was the first to connect in each trial.
@brickh
Please use http://www.pastebin.com next time so that it is not in a large comment. Can you show the IP files and config.yml for AntiMulti itself?
server.log: http://pastebin.com/KzT2LBEg
Which config?
I have tried the /add command as well as editing the files to add the names to the IP.yml [there are three people on 1 IP] as that didn't work, I tried increasing max names to 3 just in case it was not reading the other two, but no luck.
@brickh
Hmm, have you tried using /add <name> <ip> ? That should let you specify the names and IPs and should let it work.
Could you provide a copy of the server.log and the config? And possibly some of the files that are in question?
REALLY interested in getting this mod working. Downloaded it, found out it was 1.9.1 and it was not working at all. Finally saw that I didn't have 2.0.2 and then it worked [and is MUCH cleaner in terms of how it organizes userdata]. HOWEVER, the max-names do not appear to be working.
Obviously, I am trying to use this to help protect my offline server but I have several people who live together that play and was assuming that keeping the max-names and max-ips to 1, I could custom add the IPs and names to accounts that I wanted to so that everyone else was defaulted to 1. Since it wouldn't let people on a LAN connect, I turned max-names up to 3 and even added the 3 names to the respective YML file, no luck. It does not appear to be working. [I do not ever intend to allow more than 1 IP per name, however I really want to allow multiple names per IP].
We've had a major griefing incident and obviously allowing multiple names to an IP suggest that players are on a LAN, but allowing multiple IPs to a name could potentially mean it is multiple people [which is exactly what we are trying to protect against].
PLEASE fix. You're my only hope. :)
@Lord_Ralex
Yes, 1.9.3, but now I am using Beta 2.0.2. THX a lot
@virus989898
You do not have Vault on your server, which I use for perms stuff.
Second: which version is this? Appears to be 1.9.3 or something.
Error:
Second: when i disable login in config, it says me to login when i connect in ;/
Please describe your plugin's config file. I managed successfully to config the max names, but I am not the hoster and I had absolutely no idea that it existed. Also, is there a way to set the msg displayed to non-whitelisted users?
What does "Designates the player as an admin" mean? The antimulti.admin permission gives him all the other permissions?
@stgram
And that is in the config.
Max-names-per-IP is the number of accounts that can share 1 IP Max-Ips-per-name is the number of IPs 1 account can use
The admin versions of those will do the same thing, just can be set lower (or higher)
You dont get it, we are speaking about hundreds of users... We need it in the config. 3 acc per ip should be enough.