pickfit

BrowseOther

BinDiff

Open-source tool to compare binaries and find differences in disassembled code.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: Java 11 LTS
  1. download the v8 bindiff_8_amd64.deb release and extract it with dpkg-deb -x into ~/apps/bindiff (no root)

    cd ~/work && curl -sSL -o bindiff_8_amd64.deb https://github.com/google/bindiff/releases/download/v8/bindiff_8_amd64.deb && mkdir -p ~/apps/bindiff && dpkg-deb -x bindiff_8_amd64.deb ~/apps/bindiff
Where the README and reality differ
  • README: (not stated) the packaged binary is run as bindiff --ui
    What worked: Run from the packaged location with the bundled JRE on PATH: cd <extract>/opt/bindiff/bin && ./bindiff_ui --ui. Running the absolute path bin/bindiff --ui from elsewhere failed with "Missing jar file in prefix:" (the prefix is the /opt/bindiff install path, not the extract dir).

Check that it works

cd ~/work && mkdir -p out1 && ~/apps/bindiff/opt/bindiff/bin/bindiff --output_dir=$HOME/work/out1 --primary=bindiff-src/fixtures/libssl/libssl.0.9.8g.x86.gcc.3.4.6.a.BinExport --secondary=bindiff-src/fixtures/libssl/libssl.0.9.8g.x86.gcc.4.3.3.a.BinExport

The output should contain “Similarity:”.

First thing to try

cd ~/apps/bindiff/opt/bindiff/bin && PATH=$HOME/apps/bindiff/opt/bindiff/jre/bin:$PATH ./bindiff_ui --ui

What it does

  • Identify identical and similar functions
    Tested
  • Compare binaries across many architectures
    Not shown working
  • Copy function names and comments between disassemblies
    Not tested
  • Highlight changes between function variants
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Opens
  3. 1 of 4 features work
  4. Works offline

macOS and Windows: the project says it runs there; pickfit hasn’t tried it.

Good for

  • Compare binary files for x86, MIPS, ARM, PowerPC
  • Identify identical and similar functions in different binaries
  • Port function names and comments between disassemblies
  • Detect changes between two variants of same function

An alternative to Diaphora and TurboDiff.

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

It opens to its main screen

  • Replayed from scratch
  • Checked on 16 Nov 2026
  • Version BinDiff 8 (@568181968, Sep 25 2023)

When pickfit opened it, its main screen rendered. That shows it installs and starts; pickfit did not use any of its features. The launch passed again with the network off.

Differences the test machine hit

  • README: Quickstart: download prebuilt installation packages from the releases page (and the Building from Source section, cmake/ninja/Boost/Java 11/yFiles)
    In the test: The v8 release has a bindiff_8_amd64.deb; extracting it with dpkg-deb -x is enough for the CLI and the UI. Source build was not needed (it also needs BinExport, IDA SDK, Binary Ninja SDK and a commercial yFiles license for the GUI).
  • README: Java 11 is a prerequisite for the Java GUI
    In the test: The .deb bundles its own JRE under opt/bindiff/jre, but bindiff_ui only starts if a java executable is on PATH: export PATH=<extract>/opt/bindiff/jre/bin:$PATH. Without it the UI fails with "Error executing 'java': No such file or directory".
  • README: BinDiff relies on a separate disassembler (IDA Pro, Binary Ninja or Ghidra)
    In the test: The CLI diffs existing .BinExport files without a disassembler; the libssl and insider fixtures from the repo were used as inputs.
  • README: (fixtures directory is a test collection)
    In the test: fixtures/self-diff/insider.BinExport failed to parse ("parsing failed for exported file"); the insider_gcc vs insider_lcc pair worked.

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.