Remote agent used for processing distributed jobs
Switch branches/tags
Nothing to show
Clone or download
i128 Update background_worker.rb
Updating http header content-type to match gem parsing requirements
Latest commit 6c0aa19 Aug 1, 2018
Type Name Latest commit message Commit time
Failed to load latest commit information.
config add config dir May 17, 2017
control Added Basics for logging Sep 29, 2017
.gitignore remove gemfile lock from gitignore May 17, 2017 Create Jan 31, 2018
Gemfile Added Basics for logging Sep 29, 2017
Gemfile.lock Added Basics for logging Sep 29, 2017 Update May 17, 2017
Rakefile add additional agent config options May 17, 2017
agent.rb Added Basics for logging Sep 29, 2017
background_worker.rb Update background_worker.rb Aug 1, 2018
version Create version Jan 31, 2018

Hashview Agent

This is the headless agent that connects to the master instance of Hashview to support distributed cracking.

Warning! distributed support is very ALPHA. This agent only works with dev instances of Hashview!

More information about distributed support can be found here: Hashview Wiki - Distributed Cracking


We strongly suggest using RVM: \curl -sSL | bash -s stable --ruby

Networking Requirements

Agents heartbeat to the master server where your full install of Hashview is located. You'll need inbound port 4567/tcp traffic for agents to communicate.


  1. Clone the hashview-agent repo

    git clone

  2. Install gems

    gem install bundler
    bundle install

  3. Provision the agent

    RACK_ENV=production rake provision_remote_agent

    A new configuration file will be generated at config/agent_config.json. Note the UUID for the agent is generated at this time. This UUID should be treated similar to an API key.

  4. Define your master server by IP (where the full install of Hashview is located) and path to your hashcat binary. Example config below:

  "master_ip": "",
  "port": "4567",
  "uuid": "31c4ec48-e7b1-1af9-b1b0-7e1d77c57928",
  "hc_binary_path": "/home/meatball/hashcat-3.30/hashcat64.bin"
  1. Start the agent

    RACK_ENV=production ruby agent.rb

  2. Verify you see the hearbeats on your master instance under the "Agents" menu. A status of 'Pending' will exist until you've authorized the agent to join the cluster. Once Authorized, the agent will take tasks off the queue and hearbeat with its hashcat status.

Happy Cracking!