AES encryption method, unable to start the client

07/17/2019 10:34 Konsan#1
I added the AES code to package all the resource files in the Data folder, but can not start the client, start NEUZ only 2 seconds flashback, there is no log error file prompt, I do not know where the problem. Please help thank you



[Only registered and activated users can see links. Click Here To Register...]
07/22/2019 17:01 NickHough#2
Start the program in Debug mode, this should show you where the application is crashing. Do note that there are several files that changes need to be made in to ensure the encryption is decoded correctly.

You should not try using AES on these files unless you know what you're doing and can compare HEX correctly, otherwise there will be other issues down the line. You're better off using lightweight obfuscation rather then AES.
07/23/2019 00:01 Konsan#3
Quote:
Originally Posted by NickHough View Post
Start the program in Debug mode, this should show you where the application is crashing. Do note that there are several files that changes need to be made in to ensure the encryption is decoded correctly.

You should not try using AES on these files unless you know what you're doing and can compare HEX correctly, otherwise there will be other issues down the line. You're better off using lightweight obfuscation rather then AES.
Je n'utilise aucune source de chiffrement, je porte le chiffrement AES sur ma source avec une méthode de chiffrement AES normale, mais je porte le code __AES. Mais cela ne peut pas être démarré dans mon source, mais si je ne mets pas tous les fichiers que j'ai empaquetés dans le client, le journal des erreurs indique qu'il me manque quelque chose dans le client. Je pense que je devrais lire le fichier de ressources normalement, mais uniquement Juste après m'être connecté pendant quelques secondes, je ne peux que voir le passé clignoter. Je ne sais pas où est le problème, c'est peut-être que mon port n'est pas assez complet ou que je dois modifier le code.
04/30/2020 07:37 siono01#4
View the source code. I also encountered the same problem before, but it has been solved. Read the following code carefully.