YAML Metadata Warning:empty or missing yaml metadata in repo card
Check out the documentation for more information.
John-hashy Pipeline Guide
The "John-hashy" workflow represents a high-efficiency password security auditing pipeline. It combines the analytical format-ingestion capabilities of John the Ripper with the massive, GPU-accelerated brute-force throughput of Hashcat.
Pipeline Architecture
| Feature | John the Ripper (The "John" side) | Hashcat (The "Hashy" side) |
|---|---|---|
| Compute Optimization | CPU-based. Highly optimized for complex format parsing. | GPU-based. Highly optimized for parallel processing speed. |
| Primary Utility | Ingestion & Extraction. Auto-detects structures and extracts hashes. | High-Throughput Mutation. Fires billions of password guesses. |
| Optimal Use Case | Extracting raw hashes from locked archives (ZIP, PDF, Office). | Executing dictionary attacks against known cryptographic hash types. |
The Two-Phase Workflow
Phase 1: Ingestion & Hash Extraction (John the Ripper)
The raw target file (e.g., an encrypted backup) is passed through John the Ripper's specific extraction utilities (such as zip2john or office2john). This process isolates the cryptographic hash from the file metadata.
Phase 2: High-Velocity Mutation Testing (Hashcat)
The extracted hash is handed off to Hashcat. Utilizing dictionary datasets and parallel processing rules, Hashcat scales compute across the GPU architecture to rapidly test potential keys against the hash until a collision or match occurs.
Software Attribution
This technical pipeline documents the combined usage of independent open-source security tools:
- John the Ripper is developed by Openwall and distributed under the GNU General Public License (GPL v2 or later).
- Hashcat is an open-source tool distributed under the MIT License.