Zero Breach — local, read-only scanner that checks a computer for indicators of the AdFection / Candiru ad-delivered spyware campaign. No network, no admin, no dependencies.
Prepare v0.1.4 release version and verification docs
interplainseb9ce5e2b8a0
diff --git a/README.md b/README.mdindex 4417015..c8b66b0 100644--- a/README.md+++ b/README.md@@ -1,7 +1,7 @@# Zero Breach-> Release v0.1.3 adds an optional Candiru file-pattern check. See-> [its scope and validation](DETECTION-UPGRADE.md). It needs a pinned YARA-X+> Release v0.1.4 prioritizes local COM-registered files in the optional Candiru pattern check and expands Windows DNS-history coverage. See+> [the v0.1.4 scope](COVERAGE-UPGRADE.md) and [pattern validation](DETECTION-UPGRADE.md). It needs a pinned YARA-X> dependency; default checks remain standard-library-only.[](https://github.com/interplains/zero-breach/actions/workflows/tests.yml)@@ -144,7 +144,7 @@ set up (e.g. a bad indicator file).Use the official repository above and check the downloaded file before running it.-**1. Verify the publisher's signature.** Release v0.1.3 includes detached GPG+**1. Verify the publisher's signature.** Release v0.1.4 includes detached GPGsignatures for the scanner and its checksum manifest, using ArchiveGenocide'sestablished release key. Follow [SIGNING.md](SIGNING.md), and compare the fullkey fingerprint with [ArchiveGenocide's verification page](https://archivegenocide.com/verify.html).@@ -168,11 +168,11 @@ you do not have to trust the download at all; you can reproduce it:```git clone https://github.com/interplains/zero-breach.gitcd zero-breach-git checkout v0.1.3+git checkout v0.1.4python build/build.py # writes dist/zero-breach.py and prints its SHA-256```-These commands reproduce v0.1.3; substitute the matching tag for another release.+These commands reproduce v0.1.4; substitute the matching tag for another release.On macOS or Linux use `python3` for the build command.Compare the hash with that release's published hash. The development branch maycontain later changes and is not expected to reproduce an earlier release.diff --git a/SIGNING.md b/SIGNING.mdindex 54af98d..5924710 100644--- a/SIGNING.md+++ b/SIGNING.md@@ -1,17 +1,17 @@# Verifying ArchiveGenocide release signatures-Zero Breach v0.1.3 supplies detached GPG signatures for the exact released+Zero Breach v0.1.4 supplies detached GPG signatures for the exact releasedscanner and its SHA256SUMS.txt manifest. They use ArchiveGenocide's existingEd25519 release-signing key, also published on the archive's verification page.Official repository: https://github.com/interplains/zero-breach-Official release: https://github.com/interplains/zero-breach/releases/tag/v0.1.3+Official release: https://github.com/interplains/zero-breach/releases/tag/v0.1.4Independent publisher page: https://archivegenocide.com/scan/#verify-downloadEstablished key identity: https://archivegenocide.com/verify.html## Check the publisher and file-Download these three files from the v0.1.3 release into one directory:+Download these three files from the v0.1.4 release into one directory:- zero-breach.py- zero-breach.py.asc@@ -36,9 +36,9 @@ Verification must succeed using the expected ArchiveGenocide key. A warningthat the key is not certified by your own web of trust is different from abad signature; do not ignore a fingerprint mismatch or failed verification.-The expected SHA-256 of zero-breach.py v0.1.3 is:+The expected SHA-256 of zero-breach.py v0.1.4 is:- 1a1eb0e76cd2791349be9861840a5756940c3a950a134b5436bc7f9d1b50e3b8+ 5ab89ef3dda3579dfc0b4930b0d66290fdc755611afd91e28c373e30fe9996ccA signature verifies which key signed these exact bytes. It does not establishthat the program has no bugs. A checksum alone is not publisher authentication.@@ -58,14 +58,14 @@ The manifest lists the fifteen release-content files, including the optionalrequirements file and Candiru rule attribution and licence records. The manifest itself andthe added public key/signatures are not self-listed.-Public verification artifacts are also retained in release-signatures/v0.1.3/.+Public verification artifacts are also retained in release-signatures/v0.1.4/.No private key is stored in this repository or in its project backups.## Indicator updates are a separate trust pathThe manually run scan/update-iocs.py still checks HTTPS, a published SHA-256,and indicator-file validity. It does not automatically verify GPG signatures.-The signed release manifest covers the indicator file shipped with v0.1.3;+The signed release manifest covers the indicator file shipped with v0.1.4;it does not authenticate later files fetched from the development branch.## Maintainer release procedurediff --git a/build/bundle.py b/build/bundle.pyindex 539dd52..1798274 100644--- a/build/bundle.py+++ b/build/bundle.py@@ -160,7 +160,7 @@ A('import datetime')A('import sys')A('import time')A('')-A('__version__ = "0.1.3 (single-file build)"')+A('__version__ = "0.1.4 (single-file build)"')A('')A('# --- embedded indicator data ------------------------------------------------')A('# The real file is iocs/adfection_iocs.txt in the project. Its provenance')diff --git a/scan/README.md b/scan/README.mdindex ea0b00c..d90d121 100644--- a/scan/README.md+++ b/scan/README.md@@ -1,7 +1,7 @@# adint-scan-> Release v0.1.3 adds experimental, opt-in `--patterns` support. See-> [DETECTION-UPGRADE.md](../DETECTION-UPGRADE.md) for dependencies, limits and+> Release v0.1.4 improves coverage for the experimental, opt-in `--patterns` check. See+> [COVERAGE-UPGRADE.md](../COVERAGE-UPGRADE.md) and [DETECTION-UPGRADE.md](../DETECTION-UPGRADE.md) for dependencies, limits and> validation evidence. Default checks need no added packages.A local, read-only check for the published AdFection / Candiru indicators,diff --git a/scan/adint_scan/__init__.py b/scan/adint_scan/__init__.pyindex 8d4fc42..f5d6c89 100644--- a/scan/adint_scan/__init__.py+++ b/scan/adint_scan/__init__.py@@ -4,4 +4,4 @@ A clean result from this tool means "no known indicators were found in the placethat can be checked." It does NOT mean the device is clean. See SPEC-scanner.md."""-__version__ = "0.1.3"+__version__ = "0.1.4"