For Users
First, you'll need to determine what your server configuration will look like. There are two different servers that need to be run, the Queueserver and Resourceserver. Both can be run on the same system or they can be run separately, either is fine. You can also have multiple resource servers that all connect to the same Queue server. The Tools on each can be different as well, but because Go is statically compiled, all Tools are built into the resource server at compile time; however, you can turn them off in the configs. There is a lot of flexibility in the configuration, which is both good and bad as it can be hard to get started. To try and help, we have put together some basic configuration files and instructions below. To help ease the deployment of CrackLord, we have created a set of Debian Packages that will work for Ubuntu, Debian, and Kali.
Queue Server
- Add our package repository to your system using apt:
curl -s https://packagecloud.io/install/repositories/emperorcow/cracklord/script.deb.sh | sudo bash
- Now you can install the debian package for the Queue Daemon:
apt-get install cracklord-queued
- This will install the queue, the web GUI, and create a set of self-signed certificates you can use to authenticate resources you may want to connect in the future. If you have a resource on the same system, we've also tried to make it easy and have created that cert for you.
- You should now look at
/etc/cracklord/queued.conf
and the config files in/etc/cracklord/resourcemanagers/
. You will have to change any settings that you'd like for your environment. - Now you can start up the queue server by issuing the following command
service cracklord-queued start
- At this point, you'll want to get some resource servers configured and connected. If you have your own hardware, you'll need to connect to it within the GUI. Your other option is to use AWS instances that you can deploy automatically from the GUI. Be careful about watching your charges for EC2 instances in AWS!
Resource Server and Tools
- If you haven't already, you should install our apt repository:
curl -s https://packagecloud.io/install/repositories/emperorcow/cracklord/script.deb.sh | sudo bash
- Now you can install the debian package for the Resource Daemon:
apt-get install cracklord-resourced
- You will now need to edit the default configuration file at
/etc/cracklord/resourced.conf
, including enabling any relevant tool plugins. You will also need to configure the tools in/etc/cracklord/plugins/
for their specific settings. - You can now run the resource server. Please note that there may be individual configuration needs for various tools, such as getting X11 running for oclHashcat, or installing nmap, etc. See the Tool list below for links to additional information. To run the server, just:
service cracklord-resourced start
- Finally, you need to connect the resource to the queue. Resources authenticate to the Queue server using certificates. These are also used to secure communications between the queue and resource, as the transmission may contain highly sensitive information, such as hashes.
- If your resource and queue are on the same system, we've already created a hash for you. You can go to https://<QUEUESERVER> and, under resources, click connect to add the resource using localhost. If not, please see https://github.com/jmmcatee/cracklord/wiki/Creating-Resource-Certificates for additional information.