Zero Breach Toolkit 2.0.3

Superseded by 2.0.4.

Zero Breach Toolkit 2.0.3. Please update.

If you checked a phone with 2.0.0, 2.0.1 or 2.0.2 and the window showed green, please check it again. A code review found that some results said more than the check had done.

Results that said too much

• A phone nothing could be read from could show green. This happened with an empty folder when a phone type was chosen, a damaged sysdiagnose, or an Android collection with an empty app list. It now says "This phone could not be checked".
• Green now means nothing matched and every check ran. If some checks could not run, the window says "Nothing found in what could be checked" in a neutral colour and lists them. Expect to see this more often than green: many computers and phones have something that cannot be checked, and a missing check is not a clean result.
• Android crash records in current and older layouts are now read. A record that cannot be read is listed as not checked. Removed apps are now recognised in real battery history.
• A file in a layout the tool does not recognise is listed as not checked instead of being counted as read.
• The report says which file types the Standard check did not fingerprint, and a match in a phone log gives its line number and says that a mention is not proof of contact.

Other fixes

• "Update indicator lists" no longer shows "name 'feeds' is not defined". The lists were updating; the error message was wrong. Thanks to the Mac and Linux testers who reported it.
• The phone guides in the programs describe the window's own buttons, not terminal commands.
• Saving a report opens in Downloads, and explains what to do if security software blocks the save.
• Help uses the real button names in your language, and right-to-left text displays better.
• A network path pasted into the phone folder box is refused before anything contacts that server, and a planted named pipe can no longer hang the check on Linux or Mac.
• A damaged archive and very long crafted text are handled more safely.

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 this 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.

Downloads and first-launch steps: see the README. Full list: CHANGELOG.

Verify before running

zero-breach-toolkit.py SHA-256: 4dfeeb805fcd74fd476369566659b0aeb5ebc91438f537f4ad2865264e1867d4

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