Skip to content

Release 0.6.0: PyPI package, build provenance and CI - #15

Merged
debugactiveprocess merged 2 commits into
mainfrom
release-0.6.0
Nov 20, 2026
Merged

debugactiveprocess merged 2 commits into
mainfrom
release-0.6.0

Conversation

@debugactiveprocess

Copy link
Copy Markdown
Owner

Prepares the 0.6.0 release. No analyzer code changes beyond the version string; the new features are the ones already in [Unreleased] (OneNote chains, VBScript emulation, batch deobfuscation, ISO/MSI/CHM).

PyPI (pip install maldoctrace)

  • python/build_wheels.py wraps the six release binaries in platform wheels (win amd64/arm64, manylinux+musllinux x86_64/aarch64, macOS 11 x86_64/arm64). The binary is installed as the maldoctrace command; maldoctrace.analyze() / analyze_bytes() return the JSON report as a dict.
  • New pypi job in release.yml, after the GitHub Release, publishing with trusted publishing from the pypi environment (no token stored).
  • Tested locally: wheels pass twine check; the Windows and Linux (WSL) wheels install in a venv, maldoctrace version prints 0.6.0 and analyze() returns malicious/100 on the IcedID OneNote sample.

Release hardening

  • Build provenance attestations for every archive (gh attestation verify).
  • Actions pinned by commit SHA; workflow permissions reduced to what each job needs.

CI / project hygiene

  • ci.yml: gofmt, vet, tests, 30 s fuzzing on six parsers, and a wheel build + install smoke test on every PR.
  • SECURITY.md (private reporting through GitHub) and Dependabot for Go modules and actions.

Before tagging v0.6.0: the PyPI pending publisher must exist (project maldoctrace, workflow release.yml, environment pypi).

- python/: wheels that ship the release binaries (maldoctrace command and a
  small Python API), built with the standard library only
- release.yml: build provenance attestations for the archives and a PyPI job
  using trusted publishing; actions pinned by commit SHA
- ci.yml: gofmt, vet, tests, short fuzzing and a wheel smoke test on every PR
- SECURITY.md and Dependabot configuration
- Version 0.6.0 in analyze.go, CHANGELOG, README and the Debian packaging
A compound file header can declare billions of FAT or mini FAT sectors;
the parser pre-allocated buffers from those counts and a crafted file
crashed the process with an out-of-memory error. Found by the new CI
fuzzing job; the crashing input is kept as a regression case.
@debugactiveprocess
debugactiveprocess merged commit 3990d8a into main Nov 20, 2026
8 checks passed
@debugactiveprocess
debugactiveprocess deleted the release-0.6.0 branch November 20, 2026 02:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant