ghidra VS x64dbg

Let's see what our beloved software reverse engineering framework Ghidra has to show.

Define war machinery. Contributing to Ghidra?

https://github.com/NationalSecurityAgency/ghidra

Binary Ninja likewise is empty and keeps up just fine as well. It's not a coincidence that the two commercial products that are funding it are both confident enough to put their stuff online like this.

And it's no conspiracy theory or intentional sandbagging, you can see the implementation: https://github.com/decompiler-explorer/decompiler-explorer

and if anyone can improve the other tools performance we'd be happy to accept it. We reached out to the Ghidra devs: https://github.com/NationalSecurityAgency/ghidra/issues/5228 but they didn't have any silver bullets for us either.

Nice, I'll give it a closer look. My only concern so far is memory hooking (still needed for hardware registers), which on Java side was called by FilteredMemoryState [1]. In memstate.cc it looks like just the simpler MemoryState is implemented [2], and there's no equivalent to MemoryAccessFilter. But it might not be that complicated to add...

[1]: https://github.com/NationalSecurityAgency/ghidra/blob/4561e8...

[2]: https://github.com/NationalSecurityAgency/ghidra/blob/4561e8...

Several months have passed since the last part was posted. Maintainers of x64dbg have continued to improve its functionality. They also opened a task to update the development tools. So in this post, we will continue the analysis based on commit f518e50 code and, where possible, we'll compare it with the commit 9785d1a, which is accurate at the time of writing.

I have never heard anyone say anything good about the Visual Studio debugger before. Now, I'm not a Windows person but I'm not gonna argue for gdb or lldb here. RemedyBG and x64dbg are the two debuggers I've heard good things about though I've never used them because, again, not a Windows person.

[1] https://remedybg.handmade.network/

[2] https://x64dbg.com/

I'd help you out but because of circumstances I have no laptop with me. You need x86/x64 debugger to do this. This one for example Find a registration procedure and look for possible brenching to other parts of code in assembly. It's probably somewhere in the beginning. Exclude code validation and export new program version.

One interesting thing you can do is download an app like https://x64dbg.com/ or cheat engine, which will let you see the memory. You can look at the process for something you’ve made and explore it. Log a memory address from your app then go find it in the tool and interpret the bytes as an integer. Find a string and see how that works. Find a pointer, read the address it’s pointing then go look at that address. You start to see how different containers store data. I find it fascinating.

If you want to also do dynamic analysis (debugging) you can use https://x64dbg.com.

close origin and download this debugger https://github.com/x64dbg/x64dbg/releases