Free to run on your own files. Using verify in a product or a business workflow needs a licence — see Licence.
| Platform | File |
|---|---|
| macOS arm64 | verify-v0.3.2-darwin-arm64 |
| macOS amd64 | verify-v0.3.2-darwin-amd64 |
| Linux amd64 | verify-v0.3.2-linux-amd64 |
| Windows amd64 | verify-v0.3.2-windows-amd64.exe |
| Checksums | SHA256SUMS, BUILD.txt |
| Sample | sample-redacted.pdf, sample-targets.txt, sample-certificate.json |
Running it
verify needs poppler’s pdftotext on your PATH: brew install poppler on macOS,
apt install poppler-utils on Debian and Ubuntu.
On macOS the binary is not yet signed, so clear the quarantine flag and make it executable before the first run:
xattr -d com.apple.quarantine verify-v0.3.2-darwin-arm64 && chmod +x verify-v0.3.2-darwin-arm64
To check the sample:
verify -f sample-redacted.pdf -targets sample-targets.txt
It exits 1, because the sample has a drawn-box leak: a filled box painted over text that is still in the page. The certificate is written to standard output and a summary to standard error.
