![]() ![]() The strings are still encrypted, but there is a tool named dotnet tracer, to help you crack easy as like you are blind. Input the RVA ADDRESS on the rva box on the cff explorer and it will give you its offset address of the file, then change the bytes on that offset with this hex byte value 2A (IN SImple word, we ret that method, we just only use hexbyte patching.), and maybe wait also for my search and replace byte patcher to easily do this or someone can generate it or just program the tool. on SAE search for the word "broken file" it will be found by the decompiler and go to the first il code of that method,copy its RVA address. ![]() ![]() Smileīut the last problem is that it wont run. Open it on SAE and feel happy to browse on those methods and you gonna see those il codes. seeing on the statistic of the fixer that it successfully fixed and save the assembly on a directory signals us that it already done on its job. wait for the tool to fix the program, remember that it will takes a longer time to do its job since we know that confuser sucks it also defend on the program size. You still cant browse on the methods when you open it on SAE dont use reflector coz that was a trash as simple as that.ĭownload this: universal fixer, if you dont have.īrowse the decryted assembly, then click on fix just use default. its important to check on the use loadlibrary, then click on decrypt. Unpacking confuser v1.9 max settings enabled. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |