HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
boricj
ghidra-delinker-extension
Assembly2023–2026
boricj / ghidra-delinker-extension

ghidra-delinker-extension

Ghidra extension for exporting relocatable object files

2Distinct people
25Mentions
0Explicit recommenders
607GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Ghidra extension for exporting relocatable object files

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 7:27:27 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year25 dated mentions

Observed mentions: 2023-10-12 22:28:05 UTC to 2026-09-21 18:45:39 UTC.

0510152023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 13 mentions; 2 submissions, 11 comments20242025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC101
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC13211
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC505
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC606

What Hacker News says

5 sources
Well, that's a long story. I'll try and keep it short. So I've worked in my spare time for the past three years on an extremely esoteric and mind-bending reverse engineering technique I call delinking [1] and my tool for it [2] developed a small user-base. At some point I saw in a Discord server a call for papers for the SURE workshop, shitposted that it'd be funny to fry academic brains for a change, then got baited into writing it. What started out as a long paper (12 pages) with quantitative case studies quickly got cut down to the bone and then some into a short paper (6 pages) that merely introduced my take on it and two qualitative case reports, because I realized it would take an amount of work on the scale of a master's thesis to do the long one. I barely managed to get that out of the door as my usual writing style is extremely u
Read the rest
nsuited for scientific papers (it took all the might of Gemini and Copilot to even wring out something that vaguely resembles academic vernacular from my first draft). I've submitted it, exhausted and deeply unsatisfied by the compromises I've had to do under that severe time crunch. Then one month later, the reviews came in. The feedback was that the topic and my take on it were interesting; the criticisms can be summarized by saying that I've missed existing related work and it would've taken the long paper to address all the deficiencies in my paper. Fair I guess, but I definitely don't have that kind of spare time to spare on writing papers. But alongside the notification decision, something unexpected was also sent: an invitation by the program committee to present a poster at the ACM CCS 2025 conference in Taiwan. This is the kind of world-class conference with a $1800 entry ticket, happening in a convention center whose area is measured in hectares, attended by professional members of an academic, industrial or state organization, all expenses paid in a five star hotel room with a king bed. Somehow, a hobbyist who can charitably be described as a Doctor Frankenstein but with bits instead of gibs, who creates unholy chimeras of programs in his free time in spite of ABIs and common sense, received an invitation from the Hogwarts School of Witchcraft and Wizardry equivalent of the cyber-security academic world to present a poster. I can't even begin to express how utterly impossible this is. So of course I said yes and now I'm in a mad dash to get everything ready in time for the conference, three weeks from now. Bonus point: it's on the other side of the planet and in my entire adult life I've basically never got farther away than the next county (and groaning while doing so). There's even more to that story, but I'll leave it for a blog post once it's done. [1] Others call it unlinking, binary splitting or binary reassembly. [2] https://github.com/boricj/ghidra-delinker-extension
In Cormac McCarthy's tips on how to write a science paper (2019) [pdf]
This wheel: https://github.com/boricj/ghidra-delinker-extension It's a Ghidra extension that can export relocatable object files from any program selection. In other words, it reverses the work done by a linker. I originally built this as part of a video game decompilation project, having rejected the matching decompilation process used by the community at large. I still needed a way to divide and conquer the problem, which is how I got the funny idea of dividing programs. That allows a particular style of decompilation project I call Ship of Theseus: reimplementing chunks of a program one piece at a time and letting the linker stitch everything back together at every step, until you've replaced all the original binary code with reimplemented source code. It's an exquisitely deep and complex topic, chock-full of ABI tidbits and toolchains
Read the rest
shenanigans. There's next to no literature on this and it's antithetical to anything one might learn in CS 101. The technique itself is as powerful as it is esoteric, but I like to think that any reverse-engineer can leverage it with my tooling. In particular, resynthesizing relocations algorithmically is one of those problems subject to the Pareto principle, where getting 80% of them right is reasonably easy but whittling down the last 20% is punishingly hard. Since I refuse to manually annotate them, I've had to relentlessly improve my analyzers until they get every last corner case right. It's by far the most challenging and exacting software engineering problem I've ever tackled, one that suffers no hacks or shortcuts. Once I got it working, I then proceeded in the name of science to commit countless crimes against computer science with it (some of those achievements are documented on my blog). Cross-delinking in particular, that is delinking an artifact to a different platform that it originates from, is particularly mind-bending ; I've had some successes with it, but I sadly currently lack the tooling to bring this to its logical conclusion: Mad Max, but with program bits instead of car parts. Ironically, most of my users are using it for matching decompilation projects: they delink object files from an artifact, then typically launch objdiff and try to create a source file that, when compiled, generates an object file that is equivalent to the one they ripped out of the artifact. I did not expect that to happen at all since I've built this tool to specifically not do this, but I guess when everything's a nail, people will manage to wield anything as a hammer.
In Reinvent the Wheel
You can find it here: https://github.com/boricj/ghidra-delinker-extension I've demonstrated a bunch of use-cases on my blog, ranging from porting software to pervasive binary patching and pilfering application code into libraries, all done on artifacts without source code available. I have one user in particular who successfully used it on a huge (7 MiB) program in a span of a couple of weeks, most of them spent fixing bugs on my end. They then proceeded to crank up the insanity to 11 by splitting that link-time optimized artifact into pieces and swapping parts out willy-nilly. That is theoretically impossible because LTO turns the entire program into a single translation unit subject to inter-procedure optimizations, so functions will exhibit nonstandard calling conventions you can't replicate with freshly built source code, but I guess
Read the rest
anything's possible when you binary patch __usercall into MSVC. I should get back to it once work is less hectic. Delinking is an exquisitely intricate puzzle to solve algorithmically and I've managed to make that esoteric but powerful reverse-engineering technique not only scalable to megabytes worth of code, but also within reach of everyday reverse-engineers.
In Collapse OS
That assumes you have a source tree to build. Decompilation output generally is meant for human consumption and is not suitable for a compiler without significant rework and carrying out a full decompilation project (even a non-matching one) is a lot of work. This is why traditional binary patching is the usual go-to option, because it doesn't require much upfront effort to perform. The downside is that you're constrained by the memory map of the original program and contorting your modifications to fit can be a huge pain. There are alternative, less widely known techniques out there with different tradeoffs. For example, if you can make the original program bytes relocatable then you can run those through a linker and let it mend both original and new parts together. I've built tooling to help do that specifically (delinking programs bac
Read the rest
k to object files [1]), it's faster than a decompilation project because you merely need to figure out and undo all the relocation spots, but you don't get source code at the end. [1] https://github.com/boricj/ghidra-delinker-extension
In Binary modding a water dispenser to save me from pressing a button (2021)

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.