How hackerhouse-opensource/electionhacking works
• The “binpack” folder holds a multitude of executables that appear to serve numerous low-level functions (from device management to multimedia apps) that can be injected or executed on the target system.
• The “cf_card” folder contains files (including configuration files, executables, and even game/emulator demos like Doom and Invaders) that are meant to be copied onto a CompactFlash card formatted in FAT16. This is central to the injection process.
• Folders like “rom” and “extracted_certs” indicate that the project also involves analyzing or extracting data (firmware images, certificates, keys) from the system.
• The “diebold” folder includes configuration payloads and additional binaries aimed specifically at the Diebold system.
• The “utils” folder likely provides ancillary utilities for modifying or inspecting binary images (e.g., dumprom.exe, cvrtbin.exe).
Main Components
• External Interfaces:
– Hardware Debugger (e.g., an OpenOCD-compatible device like the TinCanTools FlySwatter 2)
– PCMCIA/CompactFlash Adapter – indicating the interface used to access the storage device
• Storage Media:
– CompactFlash Card – containing the “cf_card” contents which include custom executables and configuration files to be loaded onto the AccuVote TSx.
• System Firmware/ROM:
– The “rom” folder content (e.g., system.bin, nk.bin, registry_dump.txt) that represents the native firmware structure of the Diebold AccuVote TSx.
• Tools & Utilities:
– “binpack” executables – tools that perform various tasks on the target system (e.g., process management, networking utilities).
– “diebold” and “utils” tools – that support flashing or interfacing with the device.
• Security and Configuration:
– Extracted Certificates/Keys (“extracted_certs”) needed for authentication or for bypassing security in the official system software.
Relationships and Data Flows
• How the Hardware Debugger connects to the Diebold system for direct memory access or flashing.
• Flow where the “binpack” tools and additional utilities are used to extract, modify, or inject code into the device’s ROM or firmware.
• Relationship between the extracted certificates/keys and how they connect to the secure boot or authentication processes within the AccuVote TSx system.
Architectural Patterns and Design Principles
• The design mostly follows an injection or “firmware modification” architecture: a preparation phase on an external PC to produce a modifiable CompactFlash device, and an injection/execution phase on the embedded hardware.
• There is a clear separation between the preparation of tools/executables (“cf_card” and “binpack”), the hardware interfacing (debugger and adapter), and the operating environment inside the embedded system (firmware, ROM, system configuration).
Relevant Technologies and Tools
• OpenOCD and compatible debugging hardware for interfacing with the embedded device.
• WinCE (as inferred from the CF card formatting instructions and WinCE-specific executables/files) as the target OS.
• FAT16 (W95 FAT16 LBA) file system details for the CF card.
• Various executables (e.g., TaskMgrARM.exe, NesCE.exe, etc.) that illustrate the wide range of functionalities that can be injected.
Final Inclusions
• Document the role of each executable group and file grouping as they relate to the system’s modifications.
• “extensibility points” such as the role of the debugger interface and possible areas for injection or modification.