The hash of a signed Windows program is now checked against a second implementation: the test kit signs its fixtures with its own copy of the steps, covering gaps between sections, section order, data after the last section, sections that share bytes and 97 sections. A file that declares more sections than were read is refused instead of being hashed with some left out.
Normal, delay-load and bound import readers now stop at the end of the file bytes their directory maps to, require complete descriptor and forwarder records, and mark the table truncated with a warning when they don't get them. A normal import table that runs past its declared Size, or has Size 0, is still read to its terminator, as Windows does, with a warning. Names and forwarders outside the bound import directory are reported instead of read from beyond it. The resource reader shares the same mapping-length helper, unchanged.
native_publisher_show reported a signed program as changed after signing when its sections had a gap between them, because the file was hashed as one run of bytes up to the certificate table. The Authenticode hash now follows the PE/COFF specification: the headers (less the checksum and the security directory entry), then each section in the order its data sits in the file, then the data after them less the certificate table, so a gap between sections isn't hashed.
A native, pure-Rust app that shows anyone how a piece of software works, with
evidence-backed answers, then helps them rebuild it. It ships a desktop app, a
CLI and an MCP server, all driven by one engine.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>