ivx research Difflicit Desktop app
Desktop app
The website shows analyses. Diffing artifacts (git refs, binaries, firmware) happens on your computer, in the desktop app.
Install
On macOS, with Homebrew:
brew install --cask ivxlabs/tap/difflicit
Or download it from the latest release: macOS, Windows and Linux. The builds aren't code-signed yet:
- macOS: right-click the app, choose Open, then Open again.
- Windows: click More info, then Run anyway.
What it uses
Difflicit drives tools you install yourself, and tells you when one is missing:
| Tool | For | Install |
|---|---|---|
| Git | git artifacts, cloning, text diffs | usually already there |
radare2 (radiff2, r2, rabin2) | binary diffs, binary headers and sections | brew install radare2 |
| ipsw | dyld shared caches, IPSW/OTA firmware | brew install ipsw |
Your projects
With no catalog configured, the app lists your own projects: the folders in ~/Difflicit with a project file,
and any folder you opened elsewhere. Downloaded firmware and extracted shared caches are kept once, in
~/Difflicit/ipsw, and shared by every project; only the dylibs you extract are copied into a project.
Opening analyses from the website
Get a copy on the website hands an analysis to the app with a difflicit://analyze?project=…&repo=owner/name
link. Any website can open such a link, so the app asks before it clones anything. Clones go to
~/Difflicit/<owner>/<repo>, made with your own git, so private repositories clone with whatever credentials
your git already has (gh auth login, for instance).
Sandboxes
The Sandbox menu connects to a VM or a test box over VNC and shows its screen inside the app, next to the
diff: QEMU (-vnc :0 is port 5900), UTM, a cloud box, anything with a VNC server. Connections (a label, host
and port) are saved in the app. Passwords aren't: you type them when connecting, and they go straight to the
VNC server.
Signing in
Sign In opens your browser to sign in with your ivx account, and the browser hands you back to the app. See GitHub.
Build it yourself
You need Rust and Tauri's system dependencies:
npm install
npm run tauri dev # the app, live-reloading
npm run tauri build # installers in src-tauri/target/release/bundle