security passwords

[Saturate]

I have come to find that you guys, shun people that ask to many questions, but I have been looking over MS3.0.3 and 4 and I have noticed one issue, neither one are truely secure, if you choose to sell your client any player can burn a copy. If you are online on your account, and another player signs on to your account the

Code:

'prevent dupe account

works decently, but I was testing all of the code and with a small hacking tool I made acouple of months ago using C++ you can manipulate the players accounts and take another players character and save it to there own account, trade the items to the other account, and then delete it... so I am wanting to write a seperate password system for the characters so you have to enter a pass for the account and a pass for each character. Kinda like a CD-Key from starcraft.

[GIAKEN]

How does your "hacking tool" work?

[Saturate]

Pretty much it scans the client for procedures and then causes them to pull the files in to a text file, the system pulls all of the files from a server side system does not work on anything past the year 2000, but, if it does not have more then 4 security procedures for each file it can retrieve it.

[DarkX]

I highly doubt that he can account for any tool like that, I have not even seen college grads make a tool that forces the client to show the secure files on the server side, remember saturate, the server especially in MS4 is programed to double check everything the client trys, though somethings are able to get by, it does catch alot more then you really think.

[DarkX]

At the most if you want it to be more secure, make the system that you were talking about that creates CD-keys and adds them to a list everytime a player creates a account, then make that CD-key have a check like the if IP=true thing, so that no one else can use the account at the same time, just like the prevent dupe code. Everytime a cd-key is used have the server randomly generate a new one, and then have the used ones added to a list of used cd-keys that are registered to that account and cannot be used again, use common since, please do not post about using a system that was made by your hands that doubtably exists.

----edit----
Or you could always make the Config.ini or .dat(for smaller files and more security) and make the cd-key register into that file on the client side so that only the server can recieve the code from you.

[DarkX]

Well if it makes him feel better let him do something worthless