De Decompiler Pro 21 !!LINK!!

De Decompiler Pro 21 !!LINK!!


De Decompiler Pro 21

the decompiler directory has a debug version, but installing this requires the installation of the decompiler source and ghidra for the user to have to manually add them to the path. the binary installer created binaries and runtimes directories. i chose to not include the runtimes directory because it causes troubles with creating installers.

as you have indicated decompilation has been around for a long time and these techniques are available for most mature platforms (this is true of disassembly also). obfuscators are a popular option for folks seeking an additional layer of protection. i would add that explicit statements from the copyright owner about usage and decompilation is incredibly important. we have made it clear that using the decompiler does require the permission of the copyright holder and further that it is an optional feature.

of course, these hacks are not ideal: the xml injection vector could be patched in a future release of ghidra, and disabling all dead code removal leaves unwanted operations around. assuming the decompiler analysis configuration interface might later be exposed through the ghidra api, i checked which rules are necessary to produce the stack copy operations. adding the stackvars base group to the register root action is enough to produce the simplified copy ops, but without adding the deadcode base group as well, the problem of the leftover intermediate transformations remains.

these temporary copies are cleared as part of the object destructor, so i would have to either have the object destructor in place (which i dont), or find a way to change the rule to be triggered at object destruction. with those options, the decompiler has to recreate all of the stack ops again. thus, the final stack would be empty, and the rules would not be applied until you changed the code, and re-enacted the hypothetical ruleset deletion. this would cause another instance of the decompiler thread to be created, which would destroy the stack, create the nodes and lines, and delete the nodes and lines again. this all causes the nodes and lines to be forgotten and redrawn on the fly as the stack operations are created. in other words, you would have to reactivate the rules each time, which would be a problem if you were working with a compiler that had timestamps and line counts that would stop counting. because of this, i disabled this rule entirely.


Leave a comment
Stay up to date
Register now to get updates on promotions and coupons.

Shopping cart