Re: Our official stance on Copyright as it Pertains to game assets
@11, if it uses string_decrypt, its breakable. I can understand how hard it would be if your creative, but ultimately, if it tracks back to BGT's decryption functions, which it would ultimately have to do (unless they found a native DLL) is still locatable. Then its just down to figuring out what is what.
My point is, you shouldn't need to be super ultra sneaky hidy secrety about where your cryptographic logic is. You shouldn't need to hash a string, then hash that, and so on (don't do that, its a bad, bad idea). Granted, try not to store your keys in your code, either. That's half the problem. You've got AWS KMS and other key management services just for that purpose -- storing cryptographic keys. Or you can set up your own. Whatever you do, don't store your keys in your code, store them (say) right next to your encrypted text, ans an encrypted string. Be creative about where you store it, but try not to store it in your code.
-- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
