Page 1 of 1
The problem has been solved, please delete it!
Posted: Thu Oct 15, 2020 3:50 am
by xtiger
The problem has been solved, please delete it!
Re: Unity3D Game Config file error, please help me.
Posted: Thu Oct 15, 2020 4:01 am
by xtiger
The problem has been solved, please delete it!
The problem has been solved, please delete it!
Posted: Thu Oct 15, 2020 7:44 am
by xtiger
The problem has been solved, please delete it!
The problem has been solved, please delete it!
Posted: Thu Oct 15, 2020 7:45 am
by xtiger
The problem has been solved, please delete it!
Re: What encryption is used for this game configuration file?, please help me.
Posted: Fri Oct 16, 2020 4:56 pm
by peter2005
- are you sure the file is encrypted? those strings look like simple base64
- the ida screenshot is rather c++ than c#
What's the tool the last screen taken from?
Re: What encryption is used for this game configuration file?, please help me.
Posted: Sat Oct 17, 2020 9:33 am
by xtiger
The problem has been solved, please delete it!
Re: What encryption is used for this game configuration file?, please help me.
Posted: Sat Oct 17, 2020 2:51 pm
by peter2005
since it's base64 maybe you should start looking for that in game code to find decryption routine
In .dex files i found AES metioned a few times.
Re: What encryption is used for this game configuration file?, please help me.
Posted: Sun Oct 18, 2020 2:11 am
by xtiger
peter2005 wrote: ↑Sat Oct 17, 2020 2:51 pm
since it's base64 maybe you should start looking for that in game code to find decryption routine
In .dex files i found AES metioned a few times.
Sorry, I just started learning reverse engineering, I can't read pseudocode, because I'm not a programmer.Could you tell me the detailed steps to find the decryption?Or could you help me find it?Thank you so much!
The problem has been solved, please delete it!
Posted: Tue Oct 20, 2020 3:40 am
by xtiger
The problem has been solved, please delete it!
The problem has been solved, please delete it!
Posted: Tue Oct 20, 2020 3:42 am
by xtiger
The problem has been solved, please delete it!