A scalable, pluggable, and distributed queue and resource system for password cracking and other compute-intensive tasks.
CrackLord is a queue and resource system designed for scalable, distributed password cracking and other compute-intensive jobs. It load balances resources like CPU and GPU from multiple hardware systems into a single queueing service, making it easier to manage tasks across distributed environments. The system separates job management from execution through a plugin-based architecture.
Security researchers, penetration testers, and developers who need to manage distributed password cracking or other resource-intensive computational tasks across multiple systems.
Developers choose CrackLord for its pluggable, scalable architecture that simplifies managing distributed compute resources, with built-in support for tools like HashCat and John the Ripper through extensible Go plugins.
Queue and resource system for cracking passwords
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
CrackLord separates job queuing from execution via resource manager and tool plugins written in Go, enabling easy extension and integration of new tools, as highlighted in the system components.
It centralizes job submission and dispatch across multiple resources, load balancing CPU and GPU from distributed systems into a single queue for scalable compute-intensive tasks.
The project includes a published API that powers the web GUI and allows custom scripts, facilitating automation and programmatic access, as noted in the web GUI & API features.
As per the philosophy, CrackLord prioritizes making resource-intensive tasks easier to manage across environments rather than optimizing speed, ideal for orchestration.
Installation from source requires a working Go environment, downloading dependencies with Git/Mercurial, and configuring files, which can be daunting compared to drop-in solutions.
Tool plugins must be compiled in Go, meaning available tools are restricted to those contributed; adding new tools requires Go knowledge and plugin development, as admitted in the contributing section.
The README directs users to a wiki for configuration and encourages contributions for documentation, suggesting it may be incomplete or require community effort to stay current.