Repository navigation
Password Protection and CSV Reports
When password protection is enabled, ABFZ generates a separate, unique password for every single item, no password is ever reused across a batch. Passwords are:
- Built from lowercase letters and digits (
a–z,0–9) - 16 characters long by default, adjustable in the GUI before starting a job
- Generated with a cryptographically secure random number generator (.NET's
RNGCryptoServiceProvider), not a simple pseudo-random function
Password protection requires WinRAR or 7-Zip, see Supported Formats & Tool Capabilities for why, and what happens if neither is installed.
Whenever password protection is on, ABFZ writes a CSV file at the start of the job:
passwords_YYYY-MM-DD_HH-MM-SS.csv
It's placed in your chosen output folder, or, if you left the output path blank, next to the first item in the batch. It opens fine in Excel, Google Sheets, or any text editor.
Columns:
| Column | Contents |
|---|---|
| Original File | Source file or folder name |
| Archive File | Resulting archive name (or ERROR if that item failed) |
| Original Size | Size before compression (MB) |
| Archived Size | Size after compression (MB) |
| Password | The generated password for that item |
Rows are appended live as each item finishes, so if a job is cancelled partway through, the CSV still contains complete, accurate entries for everything that finished before the cancel.
If an item fails to compress, its row records ERROR in place of the archive name along with the reason (e.g. the tool's exit code), instead of a password.
- The CSV is a plain text file, treat it like any other sensitive document. Store or transmit it separately from the archives it unlocks, and delete it once passwords have been distributed or recorded elsewhere.
- ABFZ does not encrypt, upload, or otherwise protect the CSV itself, that's on you.
- Because each item gets its own password, losing or sharing one archive's password doesn't expose the rest of the batch.
© 2025–2026 Avarwand. All rights reserved.