I have zero experience reverse engineering and very little with software development. Most of my work has been in DevOps/SRE space with an emphasis on infrastructure. I am surrounded by code, but other than terraform, and the occasional python script, I don't really write much of it.
Not too long ago, I successfully reverse engineered an abandoned audio effects plugin, as well as a discontinued instrument with an onboard DSP for virtual instrument modeling. I had no idea what I was doing, but it was still amazing to get to open the black box and see what's inside and how it worked.
The plugin is nearly 1:1 as far as sound, and while I'm not going to use the code or the techniques, peeking into them gave me the insight I needed to start trying to replicate the functionality on a modern DSP.
I have my issues with generative AI as a technology, but busting open propietary software - particularly when it's abandoned and unsupported, is one of the cooler use cases I've seen for it.
teravor 47 minutes ago [-]
for LLMs, IDA Pro works better than Ghidra in my experience.
you can also steer the LLM into doing tedious but correct things like injecting code, hijacking functions, intercepting data etc to gain an understanding of what's going on if straight up disassembly doesn't appear to be going in the right direction.
have the LLM periodically write reports on all its findings and then wipe the context and reset this time with the report at hand.
bri3d 26 minutes ago [-]
The “normal” Ghidra MCP is exceptionally bad but straight scripting it headless or having an LLM build a better MCP delivers similar or better results to IDA. Ghidra emulation is much more robust which is helpful. The official IDA MCP is very well made also though and it’s definitely an easier win if you want to spend the money.
teravor 15 minutes ago [-]
you don't actually have to spend money on IDA Pro. hint: rutracker
mdswanson 34 minutes ago [-]
Just a friendly reminder that reverse engineering can have rules and regulations that are worth reviewing. For example, Apple's developer agreement specifically disallows it in certain cases.
strbean 18 minutes ago [-]
But if you go and edit EULA.txt to say "reverse engineering is expressly allowed", LLMs don't know the difference!
sksareen1 59 minutes ago [-]
[flagged]
Rendered at 01:04:37 GMT+0000 (Coordinated Universal Time) with Vercel.
Not too long ago, I successfully reverse engineered an abandoned audio effects plugin, as well as a discontinued instrument with an onboard DSP for virtual instrument modeling. I had no idea what I was doing, but it was still amazing to get to open the black box and see what's inside and how it worked.
The plugin is nearly 1:1 as far as sound, and while I'm not going to use the code or the techniques, peeking into them gave me the insight I needed to start trying to replicate the functionality on a modern DSP.
I have my issues with generative AI as a technology, but busting open propietary software - particularly when it's abandoned and unsupported, is one of the cooler use cases I've seen for it.
you can also steer the LLM into doing tedious but correct things like injecting code, hijacking functions, intercepting data etc to gain an understanding of what's going on if straight up disassembly doesn't appear to be going in the right direction.
have the LLM periodically write reports on all its findings and then wipe the context and reset this time with the report at hand.