4 Attachment(s)
[Release] Simple Account edit tool
Simple Account Tool is a tool were admins can lookup accounts and edit there pass or ban them.
There is also a ranking lookup system. this tool isnt 100% yet.
Admins are also able to connect to SQL server remotely, usefull for admins that dont got server pc acces.
Enter server ip instead of the SQL server name, u need to open port 3306 or/and 1433.
Enjoy.
Re: [Release]Simple Account edit tool
Some ideas of what you can add for the server file--
1. An Option to only allow certain IPs to connect
2. Anti-cracking option to block IP for X amount of time if too many failed login attempts
Pretty useful options to add just incase someone who isn't suppose to obtains the client portion of the account editor and tries to use it maliciously.
Re: [Release]Simple Account edit tool
I think open SQL ports to external access could be a big problem... as we know SQL is unsafe and many ppl knows how to get an unauthorized access.
btw nice job...
Re: [Release]Simple Account edit tool
Quote:
Originally Posted by
DarkKnightH20
Some ideas of what you can add for the server file--
1. An Option to only allow certain IPs to connect
2. Anti-cracking option to block IP for X amount of time if too many failed login attempts
Pretty useful options to add just incase someone who isn't suppose to obtains the client portion of the account editor and tries to use it maliciously.
Nice! ty
how could i do the anti cracking option? throu sql?
btw what else can be done trou SQL?
like setting crown?
something else?
ty
Re: [Release]Simple Account edit tool
Re: [Release]Simple Account edit tool
Re: [Release]Simple Account edit tool
Keep up the good work Mojo. Now get to work on that auto updater XD.
Re: [Release]Simple Account edit tool
Quote:
Originally Posted by
Mojo-Be
Nice! ty
how could i do the anti cracking option? throu sql?
btw what else can be done trou SQL?
like setting crown?
something else?
ty
Oh whoops, thought you had created the program a different way (RAT style, minus it being malicious though). What I had thought you did was make two exes -- one a server that wait for incoming connection requests and the other a client. The server allows certain IPs to connect and/or could have a login system built in. The client would allow the user to input an IP and a username+password for connecting to the server file created. Theoretically, one could allow all commands to pass through from client to the server so that you wouldn't have to enable remote access to SQL. It would allow for more security while also allowing for complete control over what can be modified.
As for SQL, I haven't had the time to actually mess with the SQL too much, but I'm sure a good amount can be done via it :)