Skip to content
This repository has been archived by the owner on Aug 19, 2023. It is now read-only.

Installing Hashview on Alternate Distros

Jump to bottom
ccammilleri edited this page Dec 8, 2017 · 8 revisions

Note: Only the sections that differ will be documented here.

Debian 9

  1. vim is not installed by default. Either install it or use nano.
  2. In step 2 the libmysqlclient-dev is named 'default-libmysqlclient-dev' or just run:
    sudo apt-get install git mysql-server default-libmysqlclient-dev redis-server openssl
  3. In step 3 you will need to add the '[mysqld]' header to my.cnf. Your edits to my.cnf should look like this:
[mysqld]
innodb_flush_log_at_trx_commit  = 0
innodb_file_format = Barracuda
innodb_large_prefix = 1
innodb_file_per_table=true

Centos (Amazon AMI)

Thanks to @recrudesce for documenting his steps:

So, I didn't install hashview onto a Debian box, so apt-get didn't exist etc etc. I installed onto an Amazon AMI, which has an OS based on CentOS and uses yum.

So, here's the issues I found, and here's how to overcome them !

sudo apt-get update
sudo apt-get install mysql-server libmysqlclient-dev redis-server openssl rake
[optional, but recommended]
mysql_secure_installation

OK, so libmysqlclient-dev doesn't exist, nor does redis-server. The first one is easy to fix, you just need to yum install mysql-devel.noarch. Second one is a little more complex - you need to download and run the script from https://gist.github.com/khelll/ff9461bfda8ebfdc488e (make sure you edit the version=3.2.0 line to be version=3.2.8 to get the latest version)

mysql_secure_installation will FAIL because it'll ask you for a root password, which you've not set up yet, so you need to start mysqld first via sudo service mysqld start and set a password via /usr/libexec/mysql55/mysqladmin -u root password 'newpassword' Then you can run mysql_secure_installation and enter the password you just set

my.cnf is in /etc/my.cnf not the location shown in the installation instructions.

USAGE: Other issues, the Setup asks you for the hashcat path, when actually it wants the binary name as well (ie not just the path). If you just put /opt/hashcat-3.30 in the box it'll fail to crack anything, you specifically have to put the binary name at the end of the path e.g. /opt/hashcat-3.30/hashcat64.bin

Clone this wiki locally