Zero Breach Toolkit 2.0.2

Superseded by 2.0.3. Please update: if this version showed a phone as green, check it again with 2.0.3.

Your antivirus may flag these programs. Antivirus products often wrongly flag new programs that are not code-signed yet, and some flag these. If you downloaded the file from the official release page, this is a false alarm and you can ignore it: the code is public, and each program has a public build record you can check. We have applied for free code signing and will report these false alarms to the antivirus companies. If the file came from anywhere else, do not run it and trust the warning.

Zero Breach Toolkit 2.0.2.

Fixes

• No more crash when a window can't be opened. On a Mac, trying to open the window could end the whole program ("Python quit unexpectedly"): in a remote session, and on a normal desktop with Apple's own built-in Python on some macOS versions. The check now says the window could not be opened and carries on in the terminal. On Apple's Python it also suggests installing Python from python.org.
• Clearer download steps. The README now has numbered steps for Windows, Mac and Linux, says which check to choose, and explains what a green result does and does not mean.
• German: one sentence no longer leaves an English word in it.
• For contributors: the test suite now copes with Apple's Python, and a single test file can be run on its own. Thanks to the Mac tester who reported these.

Nothing changed in what the check looks for. If you use 2.0.0, please update: it could not open encrypted iPhone backups (fixed in 2.0.1).

Downloads and first-launch steps: see the README.

Verify before running

zero-breach-toolkit.py SHA-256: bcf8459d0a6d7ecb1612e25c23abf6c676d02e086cd8af6bd7d8c7524df20aec

Each program: gh attestation verify <file> --repo interplains/Zero-Breach-Toolkit. Signed with key C24E C92B 12D6 670A 2516 065F 9B4D 5754 99AF A53C.