Case study
Untangle: a browser rebuild from REA and Ghidra evidence
An author-documented REA/Ghidra investigation of the shipped Untangle Windows binary produces a single-page playable rebuild and a claim-by-claim grading receipt. The report separates frozen findings, a later source-code answer key and a prior-knowledge audit.
- Targets
- Binary · Game
- Category
- Community REA investigations
- Relationship
- Author-reported mixed workflow
- Sources reviewed
Requirements & limits
- Prerequisites: The recorded run uses REA 6.3.0, Ghidra 12.1.4 and Windows 11 against puzzles version 20260923.616da16; the rebuild is available as a browser page.
- Testing evidence: The reported 52/54 correct claims and L3 seed fidelity are the author's grading results; ten names absent from REA output indicate possible prior-knowledge contamination.
- Limits: The 72 MB evidence export is omitted; its hash is retained. The README documents a pre-publication history rewrite and maps old commit hashes to new ones.
- License: Original puzzle binary and source retain Simon Tatham and contributors' MIT license.
About this entry
The description was reviewed against primary sources.
Primary sources
- README.md GitHub · az9713/untangle-rebuild · Revision 6e99251
- https://az9713.github.io/untangle-rebuild/receipt/rebuild-receipt.html
- https://az9713.github.io/untangle-rebuild/rebuild/index.html
More in Games
- xoreos: an open reimplementation of BioWare’s Aurora engine family · Case study
- z2rs: an incremental Rust reconstruction of Zelda II checked against an emulator · Case study
- ArkWeb: a two-game movement and collision experiment · Case study
- Batla 3D server emulator (2015 client) · Case study
- bf-private-server: a Brave Frontier revival server · Case study
- D2R Mobile: rehosting Diablo II: Resurrected’s Switch program on Apple devices · Case study