Skip to content

Refuse network paths for --iocs and --json in the single-file download - #10

Merged
interplains merged 1 commit into
mainfrom
fix/bundle-unc-guard
Oct 20, 2026
Merged

interplains merged 1 commit into
mainfrom
fix/bundle-unc-guard

Conversation

@interplains

Copy link
Copy Markdown
Owner

Summary

Follow-up to #9. The downloadable zero-breach.py has its own entry point, generated by build/bundle.py, which parses --iocs and --json itself instead of going through cli.py. The local-disk check added in #9 therefore protected source installs only; the download still accepted UNC and mapped-drive paths for both options.

Change

  • build/bundle.py: the bundled main() now refuses --iocs / --json paths that are not on a local disk, before anything is opened.
  • test_bundle_release.py: tests against a freshly built bundle — network paths are refused with nothing opened, and relative --json report.json still writes the report.

Testing

  • Full suite: 283 passed, 1 skipped.
  • Reproducible-build check passes.
  • The built dist/zero-breach.py exits 1 with a clear error for a UNC path on either option.

The downloadable single file has its own entry point, generated by
build/bundle.py, separate from the source CLI. The local-disk check for
--iocs and --json was added only to the source CLI, so the download still
accepted UNC and mapped-drive paths.

Add the same check to the bundled entry point, before anything is opened,
and test it against the built bundle: network paths are refused, and the
documented relative "--json report.json" still works.
@interplains
interplains merged commit 6ebe689 into main Oct 20, 2026
19 checks passed
@interplains
interplains deleted the fix/bundle-unc-guard branch October 20, 2026 13:12
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