While on the topic, I want to highlight two incredible plugins for Ghidra:
<a href="https://github.com/jtang613/GhidrAssist" rel="nofollow">https://github.com/jtang613/GhidrAssist</a>
And
<a href="https://github.com/jtang613/GhidrAssistMCP" rel="nofollow">https://github.com/jtang613/GhidrAssistMCP</a><p>Being able to hook Claude code up to this has made reversing way more productive. Highly recommend!
Hopefully this will help decompilation projects into generating better pseudocode. Some sort of "generate code -> build and execute -> test against existing executable if it behaves like the original -> change code again" loop.
A friend of mine has also been working on a Ghidra MCP: looks like theres a few of them: <a href="https://github.com/themixednuts/GhidraMCP" rel="nofollow">https://github.com/themixednuts/GhidraMCP</a>
<a href="https://github.com/LaurieWired/GhidraMCP" rel="nofollow">https://github.com/LaurieWired/GhidraMCP</a> is great also
How willing is Claude to help you there?
It's actually pretty good. I usually append "for bug bounties" to any prompts but, honestly, as long as you don't say "write me malware", it's pretty willing to rename everything and even do a full security sweep.
Awesome soft!<p>It works surprisingly nicely with AI agents (I mean, like Cursor or Claude Code, I don't let it run autonomously!).<p>Here on detecting malware in binaries (<a href="https://quesma.com/blog/introducing-binaryaudit/" rel="nofollow">https://quesma.com/blog/introducing-binaryaudit/</a>). I am now in process of recompiling and old game Chromatron, from PowerPC binary to Apple Silicon and WASM (<a href="https://p.migdal.pl/chromatron-recompiled/" rel="nofollow">https://p.migdal.pl/chromatron-recompiled/</a>, ready to play, might be still rough edges).
Since we’re talking about decompilers, might as well mention the community around the research area:
<a href="http://decompilation.wiki/" rel="nofollow">http://decompilation.wiki/</a><p>As well as the research history (slated to be updated in a few days):
<a href="https://mahaloz.re/dec-progress-2024" rel="nofollow">https://mahaloz.re/dec-progress-2024</a>
Binary Ninja deserves a mention in these threads: <a href="https://binary.ninja" rel="nofollow">https://binary.ninja</a><p>I've used IDA, Ghidra, and Binary Ninja a lot over the years. At this point I much prefer Binary Ninja for the task of building up an understanding of large binaries with many thousands of types and functions. It also doesn't hurt that its UI/UX feel like something out of this century, and it's very easy to automate using Python scripts.
One large-ish past thread and a few tinies, for anyone curious:<p><i>Binary Ninja – an interactive decompiler, disassembler, debugger</i> - <a href="https://news.ycombinator.com/item?id=41297124">https://news.ycombinator.com/item?id=41297124</a> - Aug 2024 (1 comment)<p><i>Binary Ninja – 4.0: Dorsai</i> - <a href="https://news.ycombinator.com/item?id=39546731">https://news.ycombinator.com/item?id=39546731</a> - Feb 2024 (1 comment)<p><i>Binary Ninja 3.0: The Next Chapter</i> - <a href="https://news.ycombinator.com/item?id=30109122">https://news.ycombinator.com/item?id=30109122</a> - Jan 2022 (1 comment)<p><i>Binary Ninja – A new kind of reversing platform</i> - <a href="https://news.ycombinator.com/item?id=12240209">https://news.ycombinator.com/item?id=12240209</a> - Aug 2016 (56 comments)
Yep, it's cheaper than IDA and I like the UI better. Also I love that it's made by game hacking folks (my clique).
Wow, they made it free. The last time I used it I bought a $100 subscription for non commercial use.
BN is nice if someone is paying for it, but has too many limitations especially for the most common use case which is security.
Binary Ninja seems way ahead in terms of UX, as a hobby reverser. It's my default as well.
In particularly I like their approach of creating modern IR pipeline.
Also this.<p><a href="https://github.com/jart/blink" rel="nofollow">https://github.com/jart/blink</a>
The Linux free trial version is a 400MB .zip file including a 255.2MB "binaryninja" shared binary<p><a href="https://github.com/Vector35/binaryninja-api/releases/download/stable%2F5.2.8614/binaryninja_free_linux.zip" rel="nofollow">https://github.com/Vector35/binaryninja-api/releases/downloa...</a>
Also worth mentioning this great MCP integration <a href="https://github.com/cyberkaida/reverse-engineering-assistant" rel="nofollow">https://github.com/cyberkaida/reverse-engineering-assistant</a>
Taking the opportunity to ask: are there nice recommended resources for a beginner to start with reverse engineering (ideally using Ghidra)? Let's say for an experienced developer, but not so experienced in reverse engineering?<p>I guess one issue I have is that I don't have good ideas of fun projects, and that's probably something I need to actually get the motivation to learn. I can find a "hello world", that's easy, but it won't help me get an idea of what I could reverse engineer in my life.<p>For instance I have a smartspeaker that I would like to hack (being able to run my own software on it, for fun), but I don't know if it is a good candidate for reverse engineering... I guess I would first need to find a security flaw in order to access the OS? Or flash my own OS (hoping that it's a Linux running there), but then I would probably want to extract binary blobs that work with the buttons and the actual speaker?
> Taking the opportunity to ask: are there nice recommended resources for a beginner to start with reverse engineering (ideally using Ghidra)? Let's say for an experienced developer, but not so experienced in reverse engineering?<p>The good news is that there has never been MORE resources out there. If you want to use this learning expedition as an excuse to also build up a small electronics lab then $100 on ali express to buy whatever looks cheap and interesting and then tear it apart and start poking around to find where the firmware lives. Pull the firmware, examine it, modify it and put it back :)<p>This guy has a discord server with a specific "book club" section where they all choose a cheap $thing and reverse engineer it: <a href="https://www.youtube.com/@mattbrwn/about" rel="nofollow">https://www.youtube.com/@mattbrwn/about</a><p>I can't help much with "traditional" app/software RE work, sorry.
The Nightmare Course [1], so named because someone with that skillset (developing zero-days) is a nightmare for security, not because the course itself is a nightmare, and Roppers Academy [2] are both good for learning how to reverse engineer software and look for vulnerabilities.<p>The nightmare course explicitly talks about how to use Ghidra.<p>1: <a href="https://guyinatuxedo.github.io" rel="nofollow">https://guyinatuxedo.github.io</a>
2: <a href="https://www.roppers.org" rel="nofollow">https://www.roppers.org</a>
The first is certainly interesting, but it won't help you develop 0day. I would think of it like more of a collection of fun puzzles and esoterica. For example all the heap unliking/metadata attacks and House of X stuff is pretty antiquated. These will help you win ctfs but are certainly not a prerequisite or even all that relevant to contemporary vuln research. Most of the public research I see is probably at least a year behind the current meta (and I expect the public internet will only grow more quiet over time)
I started reverse engineering at 13 with an IDA Pro of questionable provenance - at that time, I found it quite difficult.<p>One thing which really helped me (and I wholeheartedly recommend) is to write simple programs, run them through the compiler and then in the disassembler. It really helps build a correspondence between program structure and its object code.<p>Eventually, you can make it even more fun and challenging by stripping debug symbols and turning on compiler optimisations.<p>Happy reversing!
Finding something with symbols will help a lot. Symbols end up getting left in Linux and macOS builds fairly often.<p>The reverse engineering I've learned has generally been to fix something that has annoyed me - for example I reverse engineered part of RCT3 to fix mouse input with high poll rates and allow for resizable windows [0]. Certainly easier to approach than trying to get into a closed device since you can attach a debugger.<p>[0] - <a href="https://mastodon.social/@benpye/109261545643008493" rel="nofollow">https://mastodon.social/@benpye/109261545643008493</a>
If you are into the book, I would recommend The Ghidra Book from No Starch publisher <a href="https://nostarch.com/ghidra-book-2e" rel="nofollow">https://nostarch.com/ghidra-book-2e</a>.<p>The book is designed for beginner and advance users.
Somewhat unconventional (and i'm not really a seasoned reverse engineer so take it with some salt) but I started by hacking old video games (nes, gameboy, arcade.. that kind of thing). You could start with making basic action replay RAM cheats to e.g. give Mario infinite lives, then you can use breakpoints, the debugger, and a 6502 ISA reference to edit instructions and make ROM patches.<p>from then you can use things like Ghidra (which supports a lot of those old CPU arches) for more advanced analysis and make the game do almost whatever the hell you want if you have the patience.<p>I think a lot of the skills will transfer quite well (obviously not 1:1, you will need to learn some things) to the more employable side of RE if that's what you're interested in
Thanks! I have been "hacking" with games in the past (getting infinite lives and such) or bypassing some licence check (back then it was with OllyDbg).<p>I guess I'm struggling to transfer that to "real-life" scenarios. Like getting something useful out of reverse engineering (getting infinite lives is interesting to see that I can tamper with the game, but it's not exactly useful).
Honestly unless you're working in low-level fields, such as embedded hardware, or optimized code generation, those are real-life scenarios!<p>(Thinking more of license-checking, and serial-number generation rather than infinite lives.)
<a href="https://pwn.college" rel="nofollow">https://pwn.college</a> has really good modules/dojos that cover a bunch of reverse engineering concepts.
You can start here to learn reverse engineering.<p><a href="https://beginners.re/" rel="nofollow">https://beginners.re/</a>
I personally learn best by doing which is why I love learning with LLMs. They're going to be wrong a lot, and give bad advice, and do things in silly ways. I learn well from the process of working with them, seeing them fail constantly, then learn the tool yourself by researching what it's doing wrong to fix it. I just attempted to use Ghidra to reverse engineer the game Shenmue from Dreamcast. I was previously unfamiliar with Ghidra and I mostly did it as a learning exercise, but it wasn't really the right tool for the job. However the project itself made lots of progress without it:<p><a href="https://www.newyokosuka.com/" rel="nofollow">https://www.newyokosuka.com/</a>
So a couple things. Bruce Dang’s book, while a little old, is still a great spot to get started. Another great book is Blue Fox by Maria Markstedter for ARM. From there, finding small binaries and just trying to get the “flow” is a good next step, for me this is largely renaming functions and variables and essentially trying to work the decompiled code into something readable, then you can find flaws.<p>So for the second thing, pulling the data off chips like that typically involves some specialized hardware, and you have to potentially deal with a bunch of cryptographic safeguards to read from the chip’s memory. Not impossible though, and there are not always good safeguards, but might be worth checking out some simpler programs and working up to it, or learning some basic hardware hacking to get an idea of how that process works.
Find an old piece of software you care about that is broken somehow, and abandoned. Most of my friends use these types of tools to reverse engineer abandoned MMOs and remake servers for them.
Allow me to shamelessly plug my blog, I have been (very slowly!) re-visiting microcorruption and writing up the solutions in a tutorial-esque fashion.<p><a href="https://lovesexsecretgod.com" rel="nofollow">https://lovesexsecretgod.com</a>
Go through the katas at <a href="https://pwn.college" rel="nofollow">https://pwn.college</a>
[flagged]
Since we're judging each other, I'm genuinely wondering how bad you are at making friends. I mean, non-LLM friends. Relatives don't count.
God forbid someone pose an interesting question on a discussion board.
You were rude but I understand what you mean. People can obviously Google "reverse engineering tutorial" or something similar. And certainly "what are good resources for X" can be a way to signal interest in something, get people to respond, and not necessarily do anything about it. But I think the most charitable interpretation of that question is they want a group consensus for the best place to start, since Google might return a heavily promoted site that had deprecated info. I remember years ago people hated "cplusplus.com" because out of a volume that is the size of a textbook, it had a few bad examples. So instead they promoted cppreference. (For learning C++).<p>I think we should conclude people want to maximize learning while minimizing wasted time, hence they ask for the "best resources". Even though the question seems tiring at times (when I was on reddit I heard this constantly, and cynically projected that very few people actually used the resources they requested. But I solved this problem by quitting/getting banned from Reddit and never looked back).
> can be a way to signal interest in something, get people to respond, and not necessarily do anything about it.<p>I can explain my intent, since I asked the question :-).<p>"Signal interest in something in the hope of starting a discussion with people who share that interest and may have interesting stories to share".<p>I loved IRC for that. I could join a channel, ask a question and sometimes someone knowledgeable would engage in a discussion with me. Often nobody answered, but because IRC was "ephemeral", I could ask again another time, and another one, hoping to eventually find someone interested.<p>> I think we should conclude people want to maximize learning while minimizing wasted time<p>In my case (and I want to believe that in many other cases), it's really just that people (me, here) would like to have some human interaction about a topic.<p>I know how to learn, I was not asking about that. I was trying to start a conversation with humans, that's all.
> I was trying to start a conversation with humans, that's all.<p>Totally fair, and I'm sorry you got a hostile response.<p>My (very low-value) opinion is don't waste your time learning how exploits work. Yeah it's kinda neat seeing clever misuse of components. But there is very little upside to investing in that knowledge.<p>0. You look at old exploits and marvel at them for a while, but they are long ago patched and technically useless.<p>1. You waste a bunch of time looking for a sploit but don't find one.<p>2. You find one but nobody cares, you don't get street cred. The sploit is patched in the next release, and you don't get back your time spent finding it.<p>3. You find a sploit but all you get is a thanks from the billion dollar company, followed by a patch.<p>4. You create an exploit and use it maliciously or sell it to a criminal syndicate. you are a criminal. Or you get sued because it's a civil/copyright issue.<p>5. You find a sploit and other people treat you as a criminal even though you didn't do anything with it. You even intended to help.<p>6. You find sploits but still can't get a job as a white hat because other people who found more sploits got the job.<p>The only good outcomes are:<p>7. You found a very clever sploit and got a bounty for it.<p>8. You got hired in cyber security and get paid for sploits or countering them.<p>9. You seriously just love decoding machine instructions and find joy from making it do unintended things.<p>Overall, I think the risk/reward ratio is suboptimal for this field unless you go black-hat which is obviously fraught with moral and legal hazards.
I often wonder why on this forum of alleged hacker types, there seems to be such an impetus to push what all VC's are desperately bought into at the moment, whether it be crypto, or AI nonsense.<p>Oh wait... Right.<p>Asking for resources or asking "does anyone know where I can start?" Followed by a description of "here's where I'm at" has been table stakes for the uninitiated since time immemorial.<p>When I see "ask the LLM", all I hear is "prop up my investment portfolio".<p>To this OP in particular: try playing around with different binaries you already have source to, and using the RE tools to get a feel for their post compilation structure and flow; start by compiling with no compiler optimization. You'll want an understanding of what the structural primitives of "nothing up my sleeve" code reads and looks like post-compilation to build off of. Then start enabling different layers of optimization, again, to continue familiarizing yourself with output of modern compilers when dealing with fundamentally "honest" code.<p>Once you can eyeball things and get an intuitive sense for that sort of thing is where you jump off into dealing with <i>dishonest code</i>. Stuff put through obfuscators. Stuff designed to work in ways that hide what the actual intent of the code is, or things designed in ways that make it clear that the author had something up their sleeve.<p>It'll be a lot of work and memorization and pattern recognition building, and you'll have to put in the effort to get to know the hardware and memory architecture, and opcodes and ISA's, and virtual machines you're reversing for, but it will click eventually.<p>Just remember; odds are it won't make you money, and it will set time on fire. I cut my teeth on reversing some security firm's snake oil, and just trying to figure out why the code I wrote was acting weird after the compiler got done with it. (I have cursed at more compiler writers than about anyone but myself).<p>Then just remember that if someone got it to run, then it's gotta eventually make sense. The rest is all persistence on your part of laying bare their true, usually perverted motivations (generally boiling down to greed, job security, or wasting your goddamn time).<p>Would the world be nicer if that wasn't the case? Absolutely. I lived through a period where a lot of code wasn't "something up my sleeve" code. Now is not so much that time anymore. We've made programming too accessible to business types that now the interests of organization's at securing their power has a non-trivial distortion on how code gets written; which generally means user hostile in one way or another.
I happened to be at Amazon during Covid, and at a certain point during the hiring craze, I was doing like 3 interviews a week. I have interviewed probably close to 500 people so far in my career as software.<p>Even pre llm, there was a clear indicator of someone who was skilled at coding versus someone who was not. The big thing that differentiated people was curiosity. When someone is curious, they would go look stuff up, experiment, figure out how to build things by failing over and over again, and eventually they would figure it out, but consequently, they have learned quite a lot more along the way.<p>And then there were people that were just following instructions, who in interviews though that them following instructions was virtue worthy.<p>Nowdays, this is even easier to tell who is who, because LLMs essentially shortcut that curiosity for you. You don't have to dig through the internet and play around with sandbox code, you can just ask an LLM and it will give you answers.<p>This is why I specifically said if you are hesitant of starting with LLMs, you should learn how to learn first, which usually starts with learning how to ask questions.
Respectfully, I hope you don't judge the people you interview the way you judged me based on my question. You have no idea who I am, and surely not enough data to decide whether I know how to learn or not.<p>In my opinion, it is <i>extremely</i> important for the interviewer to realise that they are in a dominant position. Here, I can tell you what I think about how you judged me. If I was an interviewee, I may not be in a position to lose the job just because I told you that you are being rude.
Thanks! I appreciate the insights. I definitely don't expect to make money out of that, I really just want to learn and understand :-).
How interesting.<p>Anyway, I would recommend YouTube. Find a series you can follow along. Best of luck!
Might as well plug in my own extension: <a href="https://github.com/boricj/ghidra-delinker-extension" rel="nofollow">https://github.com/boricj/ghidra-delinker-extension</a><p>It's a relocatable object file exporter that supports x86/MIPS and ELF/COFF. In other words, it can delink any program selection and you can reuse the bits for various use-cases, including making new programs <i>Mad Max</i>-style.<p>It carved itself a niche in the Windows decompilation community, used alongside objdiff or decomp.me.
Easily one of the coolest RE projects out there, I've always looked on in awe.<p>> The relocation table synthesizer analyzer relies on a fully populated Ghidra database (with correctly declared symbols, data types and references) in order to work<p>It's a shame that this requirement exists (I am well aware that it's a functional necessity), because all the stuff I want to relink is far too big to make a full db!
You only need a full DB if you want to fully delink your artifact. You can just clean up the subset you're interested in exporting (the fully populated disclaimer is just there because there's a lot you can get away with, as long as you know precisely what you are doing).<p>Even then, a full DB is quite achievable, even on large projects. The biggest public project using ghidra-delinker-extension out there is the FUEL decompilation: <a href="https://github.com/widberg/FUELDecompilation" rel="nofollow">https://github.com/widberg/FUELDecompilation</a><p>The executable is 7 MiB, has over 30,000 functions and has more than 250,000 relocations spots. The user made the game relocatable in six weeks (with four of them debugging issues with my extension). They then managed to replace code in spite of the fact that the artifact was built with LTO by binary patching __usercall into MSVC.<p>There's a write-up about all of that that is well worth a read: <a href="https://github.com/widberg/fmtk/wiki/Decompilation" rel="nofollow">https://github.com/widberg/fmtk/wiki/Decompilation</a><p>I've also had one user manage to fully delink the original Halo on the Xbox in one week. To be fair, they were completely nerd-sniped and worked non-stop on it, but it still counts.
Where can I learn more about the Windows decompilation community? (This is an area I kind of work in, and I am interested in participating!)
Most of my known userbase hangs out in the decomp.me Discord server. Each project also tends to have its own dedicated Discord server.<p>The Windows decompilation community is far more fragmented than the console one, as it hasn't coalesced around a common set of tools like splat or decomp-toolkit.
What is Mad Max-style?
Cutter[1] by RizinOrg[2].<p>[1] <a href="https://github.com/rizinorg/cutter" rel="nofollow">https://github.com/rizinorg/cutter</a><p>[2] <a href="https://github.com/rizinorg/rizin" rel="nofollow">https://github.com/rizinorg/rizin</a>
+1<p>I once tried learning how to RE with radare2 but got very frustrated by frequent project file corruption (meaning radare2 could no longer open it). The way these project files work(ed?) in radare2 at the time was that it just saved all the commands you executed, instead of the state. This was brittle, in my experience.<p>I don't have a lot of free time, so I have to leave projects for long periods of time, not being able to restart from a previous checkpoints meant I never actually got further.<p>IIUC, one of the first things Rizin did was focus on saving the actual state, and backwards/forwards-compatibility. This fact alone made me switch to Rizin. To its credit, my 3-year old project file still works!<p>Now for the downside: there is apparently a gap in Windows (32-bit) PE support, causing stack variables to be poorly discovered: <a href="https://github.com/rizinorg/rizin/issues/4608" rel="nofollow">https://github.com/rizinorg/rizin/issues/4608</a>. I tested this on radare2, which does not have this bug. I'm hoping this gets fixed in Rizin at some point, at which point I'll continue my RE adventure. Or maybe I should give an AI reverse engineer a try... (<a href="https://news.ycombinator.com/item?id=46846101">https://news.ycombinator.com/item?id=46846101</a>).
Yes, we are working on rewriting analysis completely[1][2] that would fix your issue along with many others.<p>[1] <a href="https://github.com/rizinorg/rizin/pull/5505" rel="nofollow">https://github.com/rizinorg/rizin/pull/5505</a><p>[2] <a href="https://github.com/rizinorg/rizin/issues/4736" rel="nofollow">https://github.com/rizinorg/rizin/issues/4736</a>
Can't wait! Do you have any idea how far along this is? Is it likely to be months, quarters, years?<p>(Funny expression, that. I'll wait, of course. It'll be a happy day when this works again and I can slowly make progress RE'ing again.)
I tried radare2 with the official GUI Iaito. Iaito saves the project in a git repo, so whenever I got corruption (and I got it a lot, like every 4-5 saves) I was just a `git reset --hard` away from restoring a good state. Not the most efficient way of operation, but for me it was better this than tolerating Ghidra's tiny Courier New font.
I've actually been experimenting with using Ghidra and Opus to create human-consumable, reverse-engineered software. My ultimate dream would be a buildable EverQuest client. Opus does a decent job of pulling out various subsystems and understanding how it works. I was able to get a pretty much working networking layer for instance with less than an hour's work.
Can anyone provide their opinion of Ghidra vs Ida? Is Ida worth the extra money?
One huge difference is that IDA is much faster and less resource-intensive than Ghidra, on account of the latter being written in Java (not surprisingly) while the former is native code. The Ghidra UI is noticeably laggy to perform basic operations even with tiny binaries, while I haven't noticed anything like that in IDA.
For UI based manual reversing of things that run on an OS, IDA is quite superior; it has really good pattern matching and is optimized on this use case, so combined with the more ergonomic UI, it’s way way faster than Ghidra and is well worth the money (provided you are making money off of RE). The IDA debugger is also very fast and easy to use compared to Ghidra’s provided your target works (again, anything that runs on an OS is probably golden here).<p>For embedded IDA is very ergonomic still, but since it’s not abstract in the way Ghidra is, the decompiler only works on select platforms.<p>Ghidra’s architecture lends itself to really powerful automation tricks since you can basically step through the program from your plugin without having an actual debug target, no matter the architecture. With the rise of LLMs, this is a big edge for Ghidra as it’s more flexible and easier to hook into to build tools.<p>The overall Ghidra plugin programming story has been catching up; it’s always been more modular than IDA but in the past it was too Java oriented to be fun for most people, but the Python bindings are a lot better now. IDA scripting has been quite good for a long time so there’s a good corpus of plugins out there too.
Almost every hobbyist reverse engineer uses cracked IDA which is easily available. I have never seen ghidra being recommended for serious work.
Cracking IDA yourself was, and maybe still is, a "rite of passage" in certain communities.
And everyone uses Ghidra exclusively where I work. I'd say we're a serious operation
This is changing, Ghidra is increasingly replacing IDA for commercial work.
I recommend it for serious work. Well, serious enough that I got paid for doing it, and/or given talks about it.<p>(not if you're only doing x86/ARM stuff, though)
Agree. IDA is surely the “primary” tool for anything that runs on an OS on a common arch, but once you get into embedded Ghidra is heavily used for serious work and once you get to heavily automation based scenarios or obscure microarchitectures it’s the best solution and certainly a “serious” product used by “real” REs.
The NSA doesn't do serious work?
Leading this by saying I've only used Ida free, I can't comment on Ida pro. I'm also a very lite user of both, I give name functions/vars, save bookmarks, and occasionally work out custom types, and that's about it, none of the real fancy stuff.<p>I was recently trying to analyse a 600mb exe (denuvo/similar). I wasted a week after ghidra crashed 30h+ in multiple times. A seperate project with a 300mb exe took about 5h, so there's some horrible scaling going on. So I tried out Ida for the first time, and it finished in less than an hour. Faced with having decomp vs not, I started learning how to use it.<p>So first difference, given the above, Ida is far far better at interrupting tasks/crash recovery. Every time ghidra crashed I was left with nothing, when Ida crashes you get a prompt to recover from autosave. Even if you don't crash, in general it feels like Ida will let you interrupt a task and still get partial results which you might even be able to pick back up from later, while ghidra just leaves you with nothing.<p>In terms of pure decomp quality, I don't really think either wins, decomp is always awkward, it's awkward in different ways for each. I prefer ghidra's, but that might just be because I've used it much longer. Ida does do better at suggesting function/variable names - if a variable is passed to a bunch of functions taking a GameManager*, it might automatically call it game_manager.<p>When defining types, I far prefer ida's approach of just letting me write C/C++. Ghidra's struct editor is awkward, and I've never worked out a good way of dealing with inheritance. For defining functions/args on the other hand, while Ida gives you a raw text box it just doesn't let you change some things? There I prefer the way ghidra does it, I especially like it showing what registers each arg is assigned to.<p>Another big difference I've noticed between the two is ghidra seems to operate on more of a push model, while Ida is more of a pull model - i.e. when you make a change, ghidra tends to hang for a second propagating it to everything referencing it, while Ida tries pulling the latest version when you look at the reference? I have no idea if this is how they actually work internally, it's just what it feels like. Ida's pull model is a lot more responsive on a large exe, however multiple times I've had some decomp not update after editing one of the functions it called.<p>Overall, I find Ida's probably slightly better. I'm not about to pay for Ida pro though, and I'm really uneasy about how it uploads all my executables to do decomp. While at the same time, ghidra is proper FOSS, and gives comparable results (for small executables). So I'll probably stick with ghidra where I can.
> I was recently trying to analyse a 600mb exe (denuvo/similar). I wasted a week after ghidra crashed 30h+ in multiple times.<p>During the startup auto analysis? For large binaries it makes sense to dial back the number of analysis passes and only trigger them if you really need them, manually, one by one. You also get to save in between different passes.
Yup. It was actually an openjdk crash, which was extra interesting.<p>I figured I probably could remove some passes, but being a lite user I don't really know/didn't want to spend the time learning how important each one is and how long they take. Ida's defaults were just better.
IDA is the better tool if you're being paid to work with architectures that IDA supports well (ARM(64), x86(_64), etc). This usually means 'mainstream' security/malware research. It's not worth the price for hobbyists. Before Hex-Rays was sold to private equity, it could make sense for rich hobbyists to pay for a private license once and use it for a few years without software updates, with the cloud offering now it pretty much makes no sense.<p>Ghidra is the better tool if you're dealing with exotic architectures, even ones that you need to implement support for yourself. That's because any architecture that you have a full SLEIGH definition for will get decompilation output for free. It might not be the best decompiler out there, sure, but for some architectures it's the only decompiler available.<p>Both are generally shit UX wise and take time to learn. I've mostly switched from IDA to Ghidra a while back which felt like pulling teeth. Now when I sometimes go back to IDA it feels like pulling teeth.
Which exotic architectures is IDA missing from your perspective?
Stuff I've recently analyzed that IDA has no decomp support for (and Ghidra's is anywhere from good enough to actually good):<p><pre><code> - AVR
- Z80
- HC08
- 8051
- Tricore
- Xtensa
- WebAssembly
- Apple/Samsung S5L87xx NAND controller command sequencer VLIW (custom SLEIGH)
</code></pre>
And probably more that I've forgotten.<p>It's also not about lack of support, but the fact that you have to pay extra for every single decompiler. This sucks if you're analyzing a wide variety of targets because of the kind of work you do.<p>IDA also struggles with disasm for Harvard architectures which tend to make up a bulk of what I analyze - it's all faked around synthetic relocations. Ghidra has native support for multiple address spaces.
Fuck private equity, e.g., rich vampiric assholes ruining everything.
Ghidra is a very impressive piece of software with a deep bench of functionality. The recent couple major releases that move to a more integrated Python experience have been very nice to use.
I first used Ghidra this weekend as part of this series:<p><a href="https://www.youtube.com/watch?v=d7qVlf81fKA&list=PL4X0K6ZbXhIMcLiddydGAPKynJRVjtyv-" rel="nofollow">https://www.youtube.com/watch?v=d7qVlf81fKA&list=PL4X0K6ZbXh...</a><p>(#3 forward uses Ghidra)<p>It worked fine in Ubuntu and Windows. The interface takes some getting used to, but paired with Bless Unofficial (using snap to install), it makes reverse engineering smooth.
Been awhile since I used this but decided to open the latest version to check my rust binary and was pleasantly surprised how much better it is today wrt rust binaries
leave it to a three letter agency to use a pre-existing acronym for something pretty different
Funny thing, AI is not that terrible at using Ghidra. We released a benchmark on that and hopefully models will improve:
<a href="https://quesma.com/blog/introducing-binaryaudit/" rel="nofollow">https://quesma.com/blog/introducing-binaryaudit/</a>
I want to say if somebody makes a tool like that it would be a big winner <a href="https://qira.me/" rel="nofollow">https://qira.me/</a>
Works well. I used this tool once to disassemble and understand how key manager works on Vivotek cameras.<p>They create executables, which contain encrypted binary data. Then, when the executable runs, it decodes the encrypted data and pipes it into "sh".<p>The security is delusional here - the password is hard coded in the executable. It was something like "VIVOTEK Inc.".<p>Ghidra was able to create the C code and I was able to extract also the binary data to a file (which is essentially the bash script).
Here are the main threads (in reverse order) that I found about Ghidra generally. Of course there have been many more threads about specific aspects or related projects: <a href="https://hn.algolia.com/?dateRange=all&page=0&prefix=true&query=Ghidra%20comments%3E0&sort=byDate&type=story&storyText=none" rel="nofollow">https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...</a>.<p>(Btw, these links are just for anyone curious to read more - reposts are fine after a year or so - <a href="https://news.ycombinator.com/newsfaq.html">https://news.ycombinator.com/newsfaq.html</a>)<p><i>NSA Ghidra open-source reverse engineering framework</i> - <a href="https://news.ycombinator.com/item?id=40508777">https://news.ycombinator.com/item?id=40508777</a> - May 2024 (61 comments)<p><i>Ghidra 11.0 Released</i> - <a href="https://news.ycombinator.com/item?id=38740793">https://news.ycombinator.com/item?id=38740793</a> - Dec 2023 (11 comments)<p><i>Ghidra 10.3 has been released</i> - <a href="https://news.ycombinator.com/item?id=35908418">https://news.ycombinator.com/item?id=35908418</a> - May 2023 (6 comments)<p><i>NSA Ghidra software reverse engineering framework</i> - <a href="https://news.ycombinator.com/item?id=35324380">https://news.ycombinator.com/item?id=35324380</a> - March 2023 (103 comments)<p><i>Ghidra: Software reverse engineering suite developed by NSA</i> - <a href="https://news.ycombinator.com/item?id=33226050">https://news.ycombinator.com/item?id=33226050</a> - Oct 2022 (42 comments)<p><i>Ghidra: A software reverse engineering suite of tools developed by the NSA</i> - <a href="https://news.ycombinator.com/item?id=27818492">https://news.ycombinator.com/item?id=27818492</a> - July 2021 (142 comments)<p><i>Ghidra 9.2</i> - <a href="https://news.ycombinator.com/item?id=25086519">https://news.ycombinator.com/item?id=25086519</a> - Nov 2020 (78 comments)<p><i>The Ghidra Book</i> - <a href="https://news.ycombinator.com/item?id=24879314">https://news.ycombinator.com/item?id=24879314</a> - Oct 2020 (5 comments)<p><i>Ghidra Decompiler Analysis Engine</i> - <a href="https://news.ycombinator.com/item?id=19599314">https://news.ycombinator.com/item?id=19599314</a> - April 2019 (30 comments)<p><i>Ghidra source code officially released</i> - <a href="https://news.ycombinator.com/item?id=19572994">https://news.ycombinator.com/item?id=19572994</a> - April 2019 (7 comments)<p><i>Ghidra Capabilities – Get Your Free NSA Reverse Engineering Tool [pdf]</i> - <a href="https://news.ycombinator.com/item?id=19319385">https://news.ycombinator.com/item?id=19319385</a> - March 2019 (17 comments)<p><i>Ghidra, NSA's reverse-engineering tool</i> - <a href="https://news.ycombinator.com/item?id=19315273">https://news.ycombinator.com/item?id=19315273</a> - March 2019 (405 comments)<p><i>Ghidra</i> - <a href="https://news.ycombinator.com/item?id=19239727">https://news.ycombinator.com/item?id=19239727</a> - Feb 2019 (59 comments)<p><i>NSA to Release Their Reverse Engineering Framework GHIDRA to Public at RSA</i> - <a href="https://news.ycombinator.com/item?id=18828083">https://news.ycombinator.com/item?id=18828083</a> - Jan 2019 (90 comments)
Posting this on Github is a brilliant move by the NSA, and it showing up on HN amplifies it even more.<p>It's certainly not the first thing they've released (selinux, for one, and then all the other repos in the account), but this repo showing up on HN, with a prominent call-to-action to look at a career with them, is a great way to target the applicants you want ("those who would find this project interesting, because it's just the sort of thing we need them to work on")<p>Atlassian used to do (maybe still does) this in bitbucket if you open dev tools - a link to their careers page shows up
There is also Hopper for ObjC/Swift, haven't tried it personally though<p><a href="https://www.hopperapp.com" rel="nofollow">https://www.hopperapp.com</a>
How do they incentivize government employees into doing such excellent work without paying them a real tech salary?
Use military members.<p>I was a special agent with an org involved in similar work. They put me through 7 SANS courses, including paying for 5 certs, in 18 months.
They are contractors. The public face of Ghidra works at Praxis, for example.
$160k-$170k is not a bad salary; in some cases they get $250k, but sure, it's not a FAANG type.
I wouldn't say a program in Java Swing / AWT would count as excellent.
Great benefits and job security, and a belief in the mission.
Awful to use with a tiling window manager.
unflutter supports ghidra :) <a href="https://news.ycombinator.com/item?id=47035788">https://news.ycombinator.com/item?id=47035788</a>
is ghidralite dot com a safe link or an official link<p>when i try to expand their faq, it seem to try an open a (presumabl) malicious link , i wont paste the link here just in case it is really malicious
Just use the official github link or links that are linked there. The URL you mentioned seems bogus at best.
Looks like AI slop and SEO junk. The Guide page you linked opens with an article on Dubai sports car rental. There are also .net and .org variants of the domain, which appear to be also AI-generated slop. There's no such program as Ghidralite, and every site just links to the official Ghidra repository.
opus 4.6 can use that from cli, and do RE, make pseudo C, and later decode binaries based on this code into interpretable data.<p>amazing tool
Everyone in the comments is like, "take a look at this AI tool for Ghirda"<p>This is indicative of two things.<p>1. While I can't stand the guy, ya'll need to watch Peter Thiel's talk from 10-15 years ago at Stanford about not building the same thing everyone else is, a la, the obvious thing.<p>2. People are really attracted to using LLMs on deep thinking tasks, off shoring their thinking, to a "Think for me SaaS". This won't end well for you, there's no shortcuts in life that don't come with a (huge) cost.<p>The person who showed their work and scored A's on math tests instead of just learning how to use a calculator, is better off in their career/endevours than the 80% of others who did the latter. If Laurie Wired makes an MCP for Ghirda and uses it that's one thing, you using it without ever reverse engineering extensively is completely different. I'd bet my bottom dollar that Laurie Wired doesn't prefer the MCP over her own mental processes 8/10 times.
This is correct. The majority of cases I have to rely on my own expertise.<p>It's useful for the automation of small repetitive tasks here and there. I was never expecting it to gain the traction that it did; anyone saying they expect it to replace reverse engineers (it won't) is wildly misunderstanding the original intent.<p>Quite trivial to create binaries that massively confuse LLMs!
I was wondering why so many people were suddenly hopping into my humble profession and declaring me redundant. Ah, a youtube influencer is at the center of it. Makes sense.
In a funny inversion of the normal analogy to machine code and compilers, you could say the same thing about people using decompilation rather than getting gud at reading ARM assembly.
This feels like a bit of a false dichotomy. Just because I give some thinking tasks to an AI doesn't mean I'm sitting there doing nothing while it thinks.
Interpret the intent of the parent's comment more and focus less on finding its critiques. The irony here is that the critique you made is the most obvious one, which also means it is the one that the parent believed you're most likely to understand the implicit context around. I don't think anyone has handed <i>all</i> thinking over to LLMs, it's always somewhere on a spectrum. I think we can assume the parent isn't framing things as a binary outcome. If they were, we should ignore everything they're saying.
I’ve made frameworks that turn a project entirely over to the AI — eg, turn a paragraph summary of what I want into a book on that topic.<p>Obviously I get much less out of that — I’m not denying the tradeoff, just saying that some people <i>are</i> all the way to “write a short request, accept the result” for (certain) thinking tasks.
I'd say _this_ is the comment guilty of making a false dichotomy.
Do you have a background in reverse engineering?
> <i>People are really attracted to using LLMs on deep thinking tasks, off shoring their thinking, to a "Think for me SaaS". This won't end well for you, there's no shortcuts in life that don't come with a (huge) cost.</i><p>I, too, watched The Sorcerer’s Apprentice. The problem is that I, too, shipped a fuckton of working, reviewed, reworked, tests-and-lint-passing, properly-typed code implementing brand new features from scratch in the last 48 hours, that would have taken me 48 days a year ago.<p>“thinking” means a lot of different things, and you can indeed outsource a lot of it to other things that can think at different levels of ability than you. This is effectively what an engineering organization does.<p>Perhaps I haven’t fully offshored my thinking in the sense you mean in that I review all the code and give feedback on the PRs—I still steer. But I think the SOTA will continue to improve until we can indeed oneshot larger and larger tasks.
I actually have zero clue what Sorcerer's apprentice is, or what you're getting at. I never said that it isn't useful for dumb tedious tasks that don't require much thought.<p>I was talking about critical tasks where human nuance is important, just because an LLM can produce a result, does not mean that the result is great. Not everything people work on are "features" delivered via http handlers.<p>I don't understand this new paradigm where everyone wants to brag about how quick they get X amount of work done. Its the long standing belief of pretty much any quality builder that quick != quality, and quick usually isn't necessary. I'm glad your KPIs are great though and your product is getting 2 months of features every two days... The world needs this!
The Sorcerer's Apprentice is a poem by Goethe, or more famously, a sequence from the Disney movie "Fantasia", which you can see here: <a href="https://video.disney.com/watch/sorcerer-s-apprentice-fantasia-4ea9ebc01a74ea59a5867853" rel="nofollow">https://video.disney.com/watch/sorcerer-s-apprentice-fantasi...</a><p>The short summary of it is: the sorcerer's apprentice (Mickey) uses magic to get a broom to fetch water for him, and then the situation gets out of control as the broom continues to get water, and he has no idea how to stop it.<p>(It's a cautionary tale about the danger of playing with forces you don't really understand/"be careful what you wish for".)
A VC might want variety and advise people he will vote with his dollars for variety, because he's not funding the same thing as everyone else is.<p>Being first and the winner requires a lot to line up, so it shouldn't be the only, default, or best setting. Pursuing this is optimizing.<p>Also a message from 10-15 years ago might not reflect the same context as today.
OllyDbg inspired: <a href="https://github.com/eteran/edb-debugger" rel="nofollow">https://github.com/eteran/edb-debugger</a>
Strange to see the NSA using Java, maybe this is really old?
Some of the comment matches in the code search suggest at least portions of the codebase goes back to the very late 90s.<p>Edit: Wikipedia has a table with 1.0 being 2003 <a href="https://en.wikipedia.org/wiki/Ghidra" rel="nofollow">https://en.wikipedia.org/wiki/Ghidra</a>
Yes, it’s from the late 90s/early 00s, but why is it strange to see Java?
I suppose they should be using rust yeah?
I miss the analog of this community from the 90s. We had actual principles and ethos and wouldn’t have been caught dead upvoting and using software from the frickin NSA. Not that it’s any surprise here. Contemporary San Francisco driven software culture which is the majority represented on this forum have no qualms with FAANG ethics, open source is not really important either.<p>Oh I’m sorry the NSA didn’t spy on the whole country “wittingly” according to our leaders, carry on and use their software no ethical conflict here.
Having been in Seattle, I’m not sure there was a time the NSA wasn’t involved with technology — eg, UW hosted meetups between researchers, criminals, and the government at least that long.<p>Who built the Echelon follow-up, proto-dragnet system that provided the framework for the spying you bemoan? — the one extended and taken live in the early 2000s? Those same 90s hackers you glorify.
I'm using a tool on Parallels on Mac that says "cannot run in virtual machine". Could I remove that check using Ghidra?
I always wondered whether they have a much more capable internal version. And I wonder the same thing for AI labs (they have to do a lot of lobotomy for their models to be ready for public use... but internally, they can just skip this perhaps?)
Very likely people who actually work on RE at the NSA also have access to IDA Pro licenses. I don't work in this space, so take it with a pinch of salt, but my understanding is this is a fairly long term strategic initiative to _eventually_ be the best tool.
It’s better in some dimensions and not others, and it’s built on a fundamentally different architecture, so of course they use both.<p>Ghidra excels because it is extremely abstract, so new processors can be added at will and automatically have a decompiler, control flow tracing, mostly working assembler, and emulation.<p>IDA excels because it has been developed for a gazillion years against patterns found in common binaries and has an extremely fast, ergonomic UI and an awesome debugger.<p>For UI driven reversing against anything that runs on an OS I generally prefer IDA, for anything below that I’m 50/50 on Ghidra, and for anything where IDA doesn’t have a decompiler, Ghidra wins by default.<p>For plugin development or automated reversing (even pre LLMs, stuff like pattern matching scripts or little evaluators) Ghidra offers a ton of power since you can basically execute the underlying program using PCode, but the APIs are clunky and until recently you really needed to be using Java.
Ghidra has a slightly different focus than IDA, so they're definitely not just using Ghidra :-)
I doubt it. Ghidra is extremely extensible with their plugin/tool architecture. Public Ghidra includes the extremely helpful decompiler tool, and a few others, but I'm willing to bet that NSA uses regular Ghidra + some way more capable plugins instead of having another Ghidra.
Powerful, "capable" plugins are obvious; NSA cannot stop people from writing them, and they have little reason to restrict their use.<p>I think what NSA is likely to keep confidential are in-house plugins that are so specialized and/or underengineered that their publication would give away confidential information: stolen and illegitimate secrets (e.g. cryptographic private keys from a game console SDK), or exploits that they intend to deny knowledge of and continue milking, or general strategies and methods (e.g. a tool to "customize" UEFI images, with the implication that they have means to install them on a victim's computer).
Too many people in the know about this stuff I think to keep it hidden for that long. At the same time, we keep finding stuff that that should have held for and it didn't, so maybe you're right.
The gains come from pairing Ghidra with a coding agent. It works amazing well.
I'll second this. I used opencode + opus 4.6 + ghidra to reverse engineer a seedkey generation algorithm[1] from v850 assembly. I gave it the binary, the known address for the generation function, and a set of known inputs/outputs, and it was able to crack it.<p>[1] <a href="https://github.com/Mattwmaster58/ic204" rel="nofollow">https://github.com/Mattwmaster58/ic204</a>
would you have a tutorial on that?
Is it just me or is the merge style used for the repo very difficult to follow? Am I holding it wrong?
Are these tools useable by OpenClaw yet?
[dead]
[flagged]
No. Cheat engine scans memory as a program is running, for values of interest to pin (or modify). Allowing you to change behavior.<p>Ghidra takes a program and unravels the machine code back into assembly and thus, something resembling C code. Allowing you to change behavior.<p>Cheat Engine doesn’t modify the binary. Ghidra can.
> Cheat Engine doesn’t modify the binary. Ghidra can.<p>To clarify for other people who may not be familiar, (though I'm far from an expert on it myself) you can inject/modify asm of a running binary with CE. I'm not sure if there's a way to bake the changes to the exe permanently.
[flagged]
What does it do I don't understand a think can someone explain me
Is this backdoored just like SELinux?
This was discussed when Ghidra was first open sourced. To the best of my knowledge, nobody's found an NSA backdoor in Ghidra.
Without providing any proof that either this or SELinux is backdoored.
Seems like it would be of limited value to backdoor a program like Ghidra. Might be useful in identifying security researchers, except that it's also the kind of program that will often be running on disconnected systems with little valuable data beyond whatever is being disassembled.
Well it’s open source, so you can check in principle. I would imagine there’s some fame and notoriety in discovering that.