So, I have just spend my entire day looking for a sufficient plugin to suit my needs but it seems there aren't any out there. So what I would need is a plugin, that modifies the console so when a command is entered at the console level it requires a password. This is to protect the console to keep people from opping and banning the real people trying to play on the server.
The console is already protected, if it is on your computer or if you are hosting it, what would be the point of this
This is more of a bandaid solution.. Why do others have access to the console? It's better to fix that issue than this.
lazycat040 This can be done with a plugin, though if they have access to the plugins too, then they could just remove the plugin that protects the console with a password. I can attempt to do this, but as I said above, it would be useless if they have access to plugins folder. EDIT: I made a BukkitDev page for this. If anyone is interested, click me.
I thought this was an interesting idea. In some cases of hosting it at home, its usually on a spare computer or the same computer that they use, the goal of this is to 'lock' the console in case someone walks up to the computer and types into the console.
Would this be a log in/log out system, or on every command? Hopefully the former. Anyway, should be possible, if there is, say, a preprocess event for console commands. Not sure if there is though.
I used ServerCommandEvent, and for the preprocess part, I just set the command to nothing. Here's the source if you want to see how I did it. Going to be adding the login system soon. https://github.com/AssistDev/ConsoleProtect
I don't think Bukkit really focuses on on console events as the console is something every server can "trust".
There you have it. Should be fairly easy, then. Although, I just noticed this is in plugin requests, not plugin development.
My plugin prevents /op in console and a few other things. http://dev.bukkit.org/bukkit-plugins/autodeop/
Okay, I spent about 3 hours making this plugin so I hope you like it its pretty basic it has three commands one of witch is just the command that it sets the command to when you type a command when lock is on but the only commands you need to worry about is 'lock' and 'pass'. The command 'lock' opens a window that asks for a password that you want to use to avoid logging it in the console. the command pass would just be 'pass Password' if you forget the password you will just have to quit the console. this plugin was much harder than I thought so hope you like it <Edit by Moderator: Redacted mediafire url> also pm me if you get any issues EDIT: Also if you don't have any issues could you please respond because that is basically why i make these plugins, for the response EDIT by Moderator: merged posts, please use the edit button instead of double posting.
[quote uid=90708464 name="Nnnnneeeedddd" post=1763173]Okay, I spent about 3 hours making this plugin so I hope you like it its pretty basic it has three commands one of witch is just the command that it sets the command to when you type a command when lock is on but the only commands you need to worry about is 'lock' and 'pass'. The command 'lock' opens a window that asks for a password that you want to use to avoid logging it in the console. the command pass would just be 'pass Password' if you forget the password you will just have to quit the console. this plugin was much harder than I thought so hope you like it <Edit by Moderator: Redacted mediafire url> Would you mind making a plugin page for this? Or include more information.... I couldn't really understand what you were trying to say up above.
There are three commands. when the console is locked, and you type a command, it will set the command to /idonotknowthepassword witch will return you must go /pass <password> but the only command you have to worry about is 'lock' and 'pass' 'lock' locks the console and asks you for a password. then 'pass' is how you unlock it when it is locked the usage is "pass <password>" Hope this is simpler . Ned
Just thought of something. Couldn't they either A), delete the plugin, or B), discover the password? Although, your ok on b, if it isn't plaintext, but I don't know anything about hashing.
Last activity:Jul 19, 2013 Joined:Jul 19, 2013 Messages:1 That is the OP's stats, obviously there is no need for this topic at this point, practically ten days later.