This should go into the post of StarCode since your asking about that.
Tips:
1) Even with starcode or any bank security method it only cosmetic. banks are insecure because not only are banks stored on user's computer but your map is there also which means your encryption keys and encryption method is available to them.
2) I use starcode.
3) I operate under the assumption that people have already hacked my banks and thus i keep nothing that can be "game breaking" in the bank.
In the Starcode documentation there should be a list of acceptable characters in the library. if i remember, only basic characters are accepted and not the fancy ones.
The hardcode is encrypted, as well as a temporary thinly hashed security composition. If you say it is insecure, I couldn't agree with you more.
I was thinking along the lines of using more variables to confuse people who wish to tamper with them and if I can only use the basic characters, then I will hash in a redundantly repetitive way. I did find a few articles that explained starcode, I just wanted to know if you guys had a few advanced encryption tactics, that's all.
I'm glad you agree, I always want to point it out as a disclaimer, cause there r soo many mapsters who don't know.
Tip:
1) since bank hashes (signatures) can be easily broken with a free program found on Google. Make a new verification hash however you see fit. (i just run all the variable through an encryption using their signature and then a second using a password. this makes banks unique)
2) keep an eye out of http://www.d3scene.com/ they are the ones going to hack your bank first.
use map obfuscation (must be turned on in options) and put your custom encryption into a library. everyone who wants to hack your bank has to re-programm your encryption(decryption). obfuscation is a pain in the ass doing so, it won't stop it but it will hurt (if your encryption is complex enough)
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Any advanced hashing tips you guys could share?
Also one thing I want to know. Can I use various types of Unicode for my string value encryptions? and if so... Which ones?
This should go into the post of StarCode since your asking about that.
Tips:
1) Even with starcode or any bank security method it only cosmetic. banks are insecure because not only are banks stored on user's computer but your map is there also which means your encryption keys and encryption method is available to them.
2) I use starcode.
3) I operate under the assumption that people have already hacked my banks and thus i keep nothing that can be "game breaking" in the bank.
In the Starcode documentation there should be a list of acceptable characters in the library. if i remember, only basic characters are accepted and not the fancy ones.
@SoulTaker916: Go
The hardcode is encrypted, as well as a temporary thinly hashed security composition. If you say it is insecure, I couldn't agree with you more.
I was thinking along the lines of using more variables to confuse people who wish to tamper with them and if I can only use the basic characters, then I will hash in a redundantly repetitive way. I did find a few articles that explained starcode, I just wanted to know if you guys had a few advanced encryption tactics, that's all.
@Datasick: Go
I'm glad you agree, I always want to point it out as a disclaimer, cause there r soo many mapsters who don't know.
Tip:
1) since bank hashes (signatures) can be easily broken with a free program found on Google. Make a new verification hash however you see fit. (i just run all the variable through an encryption using their signature and then a second using a password. this makes banks unique)
2) keep an eye out of http://www.d3scene.com/ they are the ones going to hack your bank first.
@SoulTaker916: Go
Thank you
@Datasick: Go
use map obfuscation (must be turned on in options) and put your custom encryption into a library. everyone who wants to hack your bank has to re-programm your encryption(decryption). obfuscation is a pain in the ass doing so, it won't stop it but it will hurt (if your encryption is complex enough)