rustgenhash
rustgenhash is a tool to generate hashes on the commandline from stdio.
It can be used to generate single or multiple hashes for usage in password databases or even in penetration testing scenarios where you want to test password cracking tools. It can also help to identify the nature of a provided hash.
Install
rustgenhash is written in Rust. You can install the tool with your Rust installation using following command:
Usage
Rustgenhash has a command line interface which allows you to set the utility into a specific operating mode. The current modes are
- analyze
- benchmark
- compare-hash
- random
- stdio
- string
- file
- header
- interactive
After selecting the mode you will need to provide the -a switch for selecting a suitable hashing algorithm and a string
or file to be hashed. The stdio mode allows you to pipe to the rgh command. The tool will hash the passed
lines from the stdio (useful for hashing password lists).
The file mode supports hashing of multiple files in a directory and currently works non-recursive.
Scheme for string hashing:
# Suppress plaintext echoes for scripting workflows
Scheme for file hashing:
# Emit only digests when listing directory contents
Scheme for string hashing from stdio:
|
# Hash-only mode preserves one output token per input line
|
|
Scheme for analyzing a hash:
Scheme for generating a HHHash of a provided url:
Scheme for comparing a hash:
Scheme for comparing hash files with each other:
Scheme for benchmarking a hash algorithm:
You can list all supported algorithms over the help function.
Lastly, the tool offers the interactive mode:
Quality Audit
Rustgenhash ships with an automated audit harness that replays curated fixtures across every CLI mode to guard against logical regressions.
The audit produces deterministic artifacts under target/audit/:
summary.txt— human-readable overview with status, severity, and skip notes.summary.json— machine-readable report suitable for pipelines.issues/— (populated in later phases) markdown snippets for failures.
Use -- --case <fixture-id> to focus on a single fixture during debugging:
Fixtures that depend on non-deterministic behavior (e.g., benchmarking,
interactive flows) are marked with a skip reason and reported as SKIP in the
summary. When the audit fails, review the emitted severity, reproduction notes,
and the JSON payload to pinpoint the mismatch.
Release Readiness
Release managers must complete docs/qa/release-readiness.md before tagging:
- Ensure the GitHub Actions “Audit Harness” workflow passed on the target commit.
- Run
cargo test --test auditlocally and sync failures intodocs/qa/logic-issues.mdviascripts/audit/export_issue.sh. - Execute
scripts/audit/check_release.shto confirm zero failing fixtures and no open issues remain. - Record retest evidence (commit hashes, CI artifact URLs) in the checklist and gather maintainer sign-offs.
Contribution
If you want to contribute to this project, please feel free to do so. I am happy to accept pull requests. Any help is appreciated. If you have any questions, please feel free to contact me.