Repository navigation
Releases
BindWitness v0.1.2
BindWitness v0.1.2
This patch release adds a reproducible Perl bundled/system zlib case study and
updates the public documentation. CLI behavior, provider contracts, exit codes
and schema version 1 remain unchanged from v0.1.1.
- Real Compress::Raw::Zlib 2.103 and 2.105 workloads demonstrate how global load
order changes selected symbol providers and how upstream symbol prefixing
isolates the bundled implementation. The case includes pinned source checksums,
build provenance, full representative reports and offline replay instructions. - The validation workload now stops when either mandatory library load fails.
Eight regression scenarios cover both libraries, both versions and both load
orders, preventing failed loading from appearing to be successful isolation. - Native Bookworm AMD64 and ARM64 CI runs the case using the validated release
binary. Build evidence is archived without changing upstream filenames;
reports and configurations remain available separately. - The README and documentation explain setup, contracts, evidence limitations,
validation and release packaging without local development journals.
The release workflow validates AMD64 and ARM64 in Debian Bookworm (glibc 2.36)
and Trixie (glibc 2.41) before packaging the native Bookworm binaries. The Perl
case demonstrates selected observed bindings; it does not claim to reproduce
the upstream AlmaLinux failure or prove general ABI compatibility.
Download bindwitness-0.1.2-linux-amd64.tar.gz or
bindwitness-0.1.2-linux-arm64.tar.gz and SHA256SUMS from the release assets.
Verify the selected archive's checksum before extracting it. Each archive
contains the CLI, Apache-2.0 license, README, documentation and JSON schemas.
Workloads and source fixtures are available in the v0.1.2 source checkout.
BindWitness v0.1.1
BindWitness v0.1.1: Native Linux AMD64 Validation & Release
This compatibility milestone adds native Linux AMD64 validation and release
packaging alongside ARM64. It preserves the standard-library Go runtime,
explicit provider contracts and conservative evidence semantics.
- Four native validation jobs cover AMD64 and ARM64 in pinned Debian Bookworm
(glibc 2.36) and Trixie (glibc 2.41) containers. Other architecture/glibc
combinations remain unresolved. Ubuntu runner selection does not imply
support for the runner's native Ubuntu userspace. - Both lazy binding and explicit
LD_BIND_NOW=1profiles check correct and wrong
providers with the sameresult=12fixture output. Reports retain the explicit
linker profile and raw evidence. Binding coverage is not function execution
coverage or a call count; eager binding is never enabled automatically. - Native, offline, comparison, cancellation, identity and CPython/zlib checks
share the existing validation scripts. Bookworm checks two upstream zlib
installations on each architecture, distinguishing provider and artifact changes. - AMD64 and ARM64 archives come from their native Bookworm validation jobs in
the same workflow run. Packaging checks saved binary version and SHA-256,
ELF machine and extracted binary equality; a singleSHA256SUMScovers both
archives. No binary is rebuilt in
the release job. - A runnable AMD64 GitHub Actions example downloads and verifies the published
binary, checks an explicit required provider contract and retains the JSON
report when the CI gate fails.
All four native combinations passed in
run 37236935579
for revision 6a5cb3c09aa0a0aa7facf8758cd81a01da02ede1. Ordinary source builds
now enable AMD64 capture. Publication still requires successful completion of
the entire matrix in the release workflow's own run. Current evidence is
recorded in the validation guide.
Download bindwitness-0.1.1-linux-amd64.tar.gz or
bindwitness-0.1.1-linux-arm64.tar.gz and SHA256SUMS. Verify the selected
archive's checksum before extraction. Each archive includes the Apache-2.0
license, README, documentation, icon and JSON schemas.
Capture scope remains one controlled executable lifetime in the base linker
namespace, with immutable artifacts and the existing unload/reload and identity
limitations. A proven provider violation remains FAIL alongside independent
capture issues; insufficient evidence remains UNRESOLVED. Workload exit status
is recorded separately from the binding verdict.
Offline checks also apply the platform boundary to saved executable and observed
binding identities in older reports. Unsupported ELF32/x32 or foreign-machine
evidence remains UNRESOLVED while a proven provider violation retains FAIL.
BindWitness v0.1.0
BindWitness v0.1.0 is the first public release: regression testing for selected ELF symbol bindings in controlled Linux/glibc workloads.
- Capture real
LD_DEBUG=bindings,filesevidence, check explicit provider contracts, and compare saved observations. - Preserve ELF identities, raw traces, coverage findings, and distinct PASS, FAIL, UNRESOLVED and INFRASTRUCTURE_ERROR outcomes.
- Includes fixes for relative DSO identity, partial provider observations, argv[0], signal cleanup, report schema versions and CI artifact ownership.
The prebuilt binary is Linux ARM64. Capture is validated on glibc 2.36 and 2.41; other versions return UNRESOLVED. Scope: one trusted process in the base linker namespace with immutable artifacts. This is not a general ABI compatibility check.
Validation includes race, vet, bounded parser fuzzing, real native ELF fixtures, CPython/zlib round trips, two upstream zlib builds, and installed/release binary checks. Both Linux CI environments must pass before publication.
Download the archive and SHA256SUMS, then run sha256sum --check SHA256SUMS before extracting. The archive includes the binary, Apache-2.0 license, README, icon, documentation and JSON schemas.