Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
Alexander J. Singleton's InfoSexy tutorial with Hashcat

Alexander J. Singleton's InfoSexy Tutorial

This tutorial is a mash-up derived from several blogs and presentations:

A special thanks to the great @nstarke for once again sending me down the InfoSec rabbit-hole.

Ubuntu

Download Ubuntu 18.04 and Burn ISO

  1. Go to Ubuntu Desktop download page and download Ubuntu 18.04.
  2. After downloading the ISO file, burn the image on to a disk with unetbootin tool (Mac users) or the Rufus tool (Windows) on to a USB thumb-drive.
  3. Insert thumb-drive into mining-rig | super-computer.

Install Ubuntu on Mining Rig

  1. After turning on the mining-rig, immediately hit the F2-key.
  2. Click on the boot-menu.
  3. Make sure the sandisk device containing the Ubuntu 18.04 iso file is selected.
  4. Save and Exit

Updating Ubuntu

  1. Hit the Option-key or Windows key on keyboard and type in "Software Updater" within the Ubuntu-OS search-field and then hit enter; that should prompt the Ubuntu-updater- upon completion, select the "Install Now" button and then enter system-password.

  2. After running the Ubuntu-updater, restart the system.

  3. For the sake of thoroughness, update Ubuntu 18.04 from the command-line by running the following commands in sequence.

  • sudo apt-get update # Fetches the list of available updates
  • sudo apt-get upgrade # Strictly upgrades the current packages
  • sudo apt-get dist-upgrade
  • sudo reboot
  1. After running the above commands, restart Ubuntu or simply type sudo reboot from the command-line.

Ubuntu Preparation for SSH (Optional)

  1. Download net-tools by running sudo apt install net-tools
  2. Run ifconfig -a or ip addr show to identify the host-IP address or name to access via SSH.
  3. Prepare Ubuntu-environment for SSH
  • sudo apt-get install openssh-server
  • sudo ufw allow 22
  • sudo reboot
  1. Download nMap (optional).
  2. Run nmap -sn your-device-ip-address to ping Ubuntu instance; it should return the name of the Ubuntu-host or computer name in additon to the IP-address within the terminal output.
  • e.g. nmap -sn 10.3.1.233
  1. Run ssh -v username@your-device-ip-address or ssh -v username@computer-name
  • e.g. ssh -v alexanderjsingleton@10.3.1.233 or ssh -v alexanderjsingleton@alexanderjsingleton-ubuntu

How to Install Nvidia GeForce GTX 1080 Graphics Drivers

Updating GPU Drivers from Graphical User Interface (GUI)

  1. Hit the Activities icon within the bottom left corner of the screen and click-on "Settings" OR hit the Option-key and search for "Settings".
  2. Next click on "Details" within the "Settings" window.
  3. Since we haven't loaded any drivers yet, Ubuntu 18.04 pre-loaded the instnace with whatever your on-board CPU carried (e.g., on my rig, within the Settings > Details, the "Graphics" field displays "Intel HD Graphics 630 (Kaby Lake GT2)".
  4. After verifying the aforementioned, go back to the Activites-page within the lower left-corner of the desktop and select "Software & Updates" or hit Option-key and search for "Software & Updates".
  5. Within the Software & Updates window, click on the "Additional Drivers" tab.
  6. After a few moments, Ubuntu will return a suggested driver to download- by default it will select the second option radio-button parenthetically described as (open source) but you want the radio-button option parenthetically described as "proprietary, tested" (e.g. in my case it was "Using NVIDIA driver metapackage from nvidia-driver-390 (proprietary, tested).
  7. After selecting the previously mentioned radio-button option, select "Apply Changes" and then reboot the computer.
  8. After rebooting the computer, go back to Settings > Details- verify that the new drivers were installed by checking Graphics description field (it should say (nvidia-driver-390).
  9. Go back to the Activites-icon page within the lower left-corner of the desktop and select "Nvidia X Server Settings" from the application menu; click on the "Prime Profiles" tab on the left-pane, and then select Intel card on the right-pane.
  10. Select the NVIDIA (Performance Mode) radio-button and then close the window.
  11. Proceed to 'Installing Hashchat' Section.

Updating GPU Drivers from the Command-Line

  1. Access the Terminal.
  2. Run sudo lshw -c display OR sudo lshw -c video to display the Ubuntu 18.04 stock-drivers loaded for the Nvidia GeForce GTX 1080 GPU cards.
  3. Since we haven't installed any drivers from the command-line yet, the driver-detail within the configuration field should display "driver=nouveau".
  4. Run sudo ubuntu-drivers devices
  5. After running the above command, only two drivers will be displayed (e.g. 'nvidia-driver-390 - distro non-free recommended' and 'xserver-xorg-video-nouveau - distro free builtin'); we want the latter 'non-free recommended'- so run sudo apt install nvidia-driver-version-number (e.g. sudo apt install nvidia-driver-390).
  6. After installing the drivers from the command-line, reboot the computer by running sudo shutdown -r now.
  7. If after rebooting your welcome-screen hangs, click on the settings-wheel icon, select the "Ubuntu on wayland" and then re-enter password.
  8. Access the terminal and run sudo lshw -c display; the driver field should now display "nvidia" instead of "nouveau".

Installing the Nvidia CUDA Toolkit 10.0

Installing the Nvidia CUDA Toolkit 10.0 for Ubuntu 18.04 - Option A (Recommended)

  1. sudo apt update && apt dist-upgrade -y && reboot
  2. lspci -v
  3. sudo apt install -y ocl-icd-libopencl1 nvidia-driver nvidia-cuda-toolkit.
  • e.g. sudo apt install -y ocl-icd-libopencl1 nvidia-driver-390 nvidia-cuda-toolkit
  1. nvidia-smi
  2. sudo reboot
  3. Access terminal and enter the following commands in sequence:
  • sudo add-apt-repository ppa:graphics-drivers/ppa
  • sudo apt-get update
  • sudo apt-get install mesa-common-dev
  • sudo apt-get install freeglut3-dev
  1. Reboot the computer by running sudo reboot

Installing the Nvidia CUDA Toolkit 10.0 for Ubuntu 18.04 - Option B

  1. Go to Nvidia CUDA Toolkit 10.0 for Ubuntu 18.04.
  2. Select the following Select Target Platform Window: Linux > X86_64 > Ubuntu > 18.04 > runfile (local)
  • To check your OS architecture run uname -a it should return "x_86_64" within the terminal display.
  1. Download the Base Installer (2.0 GB) by click on the Download button.
  2. Access Terminal and close X Server to avoid errors while updating nVidia driver by running sudo init 3; a black-screen will appear and prompt you to enter your Ubuntu username and password- please enter.
  3. After logging-in, run cd ~/Downloads.
  4. Run sudo sh cuda_10.0.130_410.48_linux.run
  5. Scroll down to accept the conditions by holding down the "Return" key or space-bar- upon scrolling to the bottom, type: accept; alternatively, you can hit 'CTRL + D' to bypass scrolling.
  6. Install the CUDA 10.0 Toolkit by enter y
  7. Do you want to Install the OpenGL Libraries y
  8. Do you want to run nvidia-xconfig? Enter y
  9. Install the CUDA Toolkit? Enter y
  10. Unless otherwise preferred, hit the "Return" key to enter the specified default absolute-path (e.g. /usr/local/cuda-10.0).
  11. Enter y to install a symbolic link at /usr/local/cuda.
  12. Enter y to Install the CUDA 10.0 Samples
  13. Hit the "Return" key to enter CUDA Samples default location-path (e.g. /home/alexanderjsingleton).
  14. After the install, open the X Server by running sudo init 5; if for whatever reason you're unable to reboot the computer after installing the CUDA 10.0 Toolkit, turn-off the computer and reboot- remember to click on the Settings icon and select "Ubuntu on wayland" before entering the username and password.
  15. Access terminal and enter the following commands in sequence:
  • sudo add-apt-repository ppa:graphics-drivers/ppa
  • sudo apt-get update
  • sudo apt-get install mesa-common-dev
  • sudo apt-get install freeglut3-dev
  1. Reboot the computer by running sudo shutdown -r now

Installing OpenCL™ Runtimes for Intel® Processors

Installing OpenCL™ Runtimes for Intel® Processors - Option A (Recommended)

  1. Check your CPU system processor architecture by running sudo lscpu to identify the class of CPU e.g. "Intel (R) Core (TM) i7-7700 CPU @ 3.60Ghz"- alternatively, you can go to Settings > Details which will also reveal the CPU-family (e.g. Intel (R) HD Graphics 630 (Kaby Lake GT2)).
  2. Go to the Intel Developer Zone and scroll down to the corresponding download link for your system; assuming you're running Ubuntu 18.04 and have a Intel Core-class CPU, scroll down to "Linux* OS Ubuntu* 16.04.x (deb)" and click on the Github link for 18.46.11837 Runtimes to access the runtime-packages to download.
  3. There should be instructions within the aforementioned Github repo- or you can proceed with the following in the next steps.
  4. cd ~/Desktop
  5. mkdir neo
  6. cd neo
  7. sudo wget https://github.com/intel/compute-runtime/releases/download/18.46.11837/intel-gmmlib_18.4.0.348_amd64.deb
  8. wget https://github.com/intel/compute-runtime/releases/download/18.46.11837/intel-igc-core_18.44.1060_amd64.deb
  9. wget https://github.com/intel/compute-runtime/releases/download/18.46.11837/intel-igc-opencl_18.44.1060_amd64.deb
  10. wget https://github.com/intel/compute-runtime/releases/download/18.46.11837/intel-opencl_18.46.11837_amd64.deb
  11. Install the packages by running sudo dpkg -i *.deb.
  12. Restart the system by running sudo reboot.

Installing OpenCL™ Runtimes for Intel® Processors - Option B

  1. Go to Intel OpenCL Runtimes website and scroll down to the bottom of the page to Download Intel CPU Runtime for OpenCL Applications 18.1 for LINUX OS (64-bit only).
  2. After downloading the OpenCL Runtimes for Intel Processors, cd ~/Downloads
  3. Run sudo tar -xzf l_opencl_p_18.1.0.013.tgz to unpack the tgz file- please note, the OpenCL file version may update since the time as of this gist (ie as of this gist, the version is 18.1.0.013.)
  4. cd l_opencl_p_18.1.0.013
  5. Run sudo ./install.sh
  6. A welcome screen is prompted- hold-down the "Enter" key until able to input select "2" for "I do NOT consent to the collection of my Information"
  7. Hit "1"
  8. Hit "1"
  9. Hit "Enter" and then restart the computer.
  10. If any additional Intel OpenCL errors are encountered after testing hashcat, go to section 'Installing OpenCL™ Runtimes for Intel® Processors - B'- if not, proceed with section "Testing Hashcat"

Hashcat

Downloading Hashcat Binaries - Option A (Recommended)

  1. Download the latest version of hashcat- scroll down to the bottom and download the version at the top of the table (as of this gist, the latest version is v5.1.0.7- be sure to download the "binaries" version of Ubuntu); use the wget command to download the latest version of hashcat from the hashcast website (e.g. wget https://hashcat.net/files/hashcat-5.1.0.7z- be sure to cd into the Downloads folder for the sake of consistency).
  2. Access the download-directory: cd ~/Downloads
  3. If you haven't already, download p7zip: sudo apt install p7zip
  4. Assuming you're still in the Downloads folder, run sudo p7zip -d hashcat-5.1.0.7z to unzip (if that command didn't work, simply right-click and extract file within the Downloads folder).
  5. Access the unzipped hashcat folder by running cd hashcat-5.1.0.7z
  6. Next run ls /usr/bin/ | grep -i hash
  7. Run sudo cp hashcat64.bin /usr/bin/
  8. sudo ln -s /usr/bin/hashcat64.bin /usr/bin/hashcat
  9. sudo cp -Rv OpenCL/ /usr/bin/
  10. sudo cp hashcat.hcstat2 /usr/bin/
  11. sudo cp hashcat.hctune /usr/bin/

Downloading Hashcat from Ubuntu Repository - Option B

Alternatively, you may download hashcat from the Ubuntu repository by simply running sudo apt-get install hashcat; however, this will more than likely download a deprecated version of hashcat.

Testing Hashcat

  1. Test hashcat, by running sudo hashcat --benchmark.
  2. As of this gist, hashcat is reporting that Intel's OpenCL runtime (GPU only) is currently broken and they are currently waiting for updated OpenCL drivers from Intel; if you encounter that error message try running sudo hashcat --benchmark --force that should successfully override any OpenCL issues.
  3. After running sudo hashcat --benchmark or sudo hashcat --benchmark --force the terminal output will report hashrates for given hash-algorithms (eg. 'MD5 560.4 KH/s', 'SHA1 149.4 MH/s', 'SHA2-256 72485.9 Mh/s' etc.)
  4. Hit CTRL + C to stop benchmark testing.

Creating Password Hashes

  1. Go to the Desktop by running cd ~/Desktop
  2. Create a new folder within the desktop (e.g. mkdir infosexy).
  3. cd infosexy
  4. Create a new folder within infosexy directory for the password dictionary (e.g. mkdir skull)
  5. cd skull
  6. Go to skullsecurity and download the 'rockyou.txt' password dictionary.
  7. Assuming you downloaded the 'rockyou.txt' file go to the 'Downloads' folder: (e.g.cd ~/Downloads).
  8. Run bzip2 -d rockyou.txt.bz2 to unpack the file-folder.
  9. Copy the 'rockyou.txt' dictionary from the Downloads-folder to the destination skull-folder- easiest way to do this is launch two terminals by opening another terminal-window from Terminal (e.g. CTRL + ALT + T) and then enter pwd from both terminal-windows to identify their respective paths.
  10. Copy source-folder file 'rockyou.txt' by running the cp command between file-paths (e.g. cp /home/alexanderjsingleton/Downloads/rockyou.txt /home/alexanderjsingleton/infosexy/skull).
  11. Run ls to confirm file transfer.
  12. Go back into the infosexy folder (e.g. cd ..)

Cracking the MD5 Hash Algorithm

  1. Within the infosexy directory, run the following commands below in sequence to create password hashes encrypting the passwords with the MD5 hash-algorithm.
  2. echo -n “Password” | md5sum | tr -d ” -” >> target_hashes.txt
  3. echo -n “HELLO” | md5sum | tr -d ” -” >> target_hashes.txt
  4. echo -n “MYSECRET” | md5sum | tr -d ” -” >> target_hashes.txt
  5. echo -n “Test1234″ | md5sum | tr -d ” -” >> target_hashes.txt
  6. echo -n “P455w0rd” | md5sum | tr -d ” -” >> target_hashes.txt
  7. echo -n “GuessMe” | md5sum | tr -d ” -” >> target_hashes.txt
  8. echo -n “S3CuReP455Word” | md5sum | tr -d ” -” >> target_hashes.txt
  9. Run cat target_hashes.txt to display all of the encrypted password with the md5sum algorithm within the Terminal window.
  10. Run sudo hashcat -m 0 -a 0 -o cracked.txt target_hashes.txt skull/rockyou.txt
  11. I have 8 * Nvidia Asus GeForce GTX 1080 * 8 GB GPUs on my mining-rig- cracking-time may vary per computer; I cracked this set within less than one second- needless to say that is really fast.
  12. Run sudo cat cracked.txt to reveal the hash key-value-pairs corresponding to the encrypted passwords within the Terminal window.

Cracking the SHA256 Hash Algorithm

  1. Within the infosexy directory, run the following commands below in sequence to create password hashes encrypting the passwords with the SHA256 hash-algorithm.
  2. echo -n “Password” | sha256sum | tr -d ” -” >> target_hashes-2.txt
  3. echo -n “HELLO” | sha256sum | tr -d ” -” >> target_hashes-2.txt
  4. echo -n “MYSECRET” | sha256sum | tr -d ” -” >> target_hashes-2.txt
  5. echo -n “Test1234″ | sha256sum | tr -d ” -” >> target_hashes-2.txt
  6. echo -n “P455w0rd” | sha256sum | tr -d ” -” >> target_hashes-2.txt
  7. echo -n “GuessMe” | sha256sum | tr -d ” -” >> target_hashes-2.txt
  8. echo -n “S3CuReP455Word” | sha256sum | tr -d ” -” >> target_hashes-2.txt
  9. Run cat target_hashes-2.txt to display all of the encrypted passwords with the SHA256 algorithm within the Terminal window.
  10. Run sudo hashcat -m 1400 -a 0 -o cracked-2.txt target_hashes-2.txt skull/rockyou.txt
  11. I have 8 * Nvidia Asus GeForce GTX 1080 * 8 GB GPUs on my mining-rig- cracking-time may vary per computer; I cracked the first hash for "Password" within less than one second- needless to say that is really fast, considering SHA256 is the same encryption-grade protecting the Bitcoin network.
  12. Run sudo cat cracked-2.txt to reveal the hash key-value-pairs corresponding to the encrypted password within the Terminal window.

Congratulations

Congratulations, you can now crack a hash- hope you learned something.

@rdgeno12

This comment has been minimized.

Copy link

rdgeno12 commented Oct 9, 2019

I can't get Unbuntu, Kali Linux, or Windows 10 Pro to use my GPU when I run Hashcat, and it is not running anywhere near correct when it does run.(I have to enter some of the info backwards.) Here is hopefully all the relevant information.
Computer
HP Desktop Series 8200
OS
Ubuntu 18.04
Processor
3.1 GHz Intel Core i5
RAM
Corsair Vengance Pro Series 24 GB DDR3
Hard drive
Seagate 500 GB SSD
GPU
4 GB AMD RX 560 LP
I run this command,
sudo hashcat -m 2500 -a 0 q.hccapx rockyou.txt -w 3
and get this. with -a 0.

OpenCL Platform #1: Intel(R) Corporation

  • Device #1: Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz, 6011/24046 MB allocatable, 4MCU

Hashes: 3 digests; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Rules: 1

Applicable optimizers:

  • Zero-Byte
  • Single-Hash
  • Single-Salt
  • Slow-Hash-SIMD-LOOP

Minimum password length supported by kernel: 8
Maximum password length supported by kernel: 63

Watchdog: Hardware monitoring interface not found on your system.
Watchdog: Temperature abort trigger disabled.

Starting attack in stdin mode...

Session..........: hashcat
Status...........: Running
Hash.Type........: WPA-EAPOL-PBKDF2
Hash.Target......:Qxxxx (AP:2c:99:24:55:be:19 STA:94:27:90:09:78:a9)
Time.Started.....: Tue Oct 8 12:27:12 2019 (10 secs)
Time.Estimated...: Tue Oct 8 12:27:22 2019 (0 secs)
Guess.Base.......: Pipe
Speed.#1.........: 0 H/s (0.00ms) @ Accel:1024 Loops:512 Thr:1 Vec:4
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 0
Rejected.........: 0
Restore.Point....: 0
Restore.Sub.#1...: Salt:0 Amplifier:0-0 Iteration:0-512
Candidates.#1....: [Copying]

Session..........: hashcat
Status...........: Running
Hash.Type........: WPA-EAPOL-PBKDF2
Hash.Target......: Qxxxx (AP:2c:99:24:55:be:19 STA:94:27:90:09:78:a9)
Time.Started.....: Tue Oct 8 12:27:12 2019 (20 secs)
Time.Estimated...: Tue Oct 8 12:27:32 2019 (0 secs)
Guess.Base.......: Pipe
Speed.#1.........: 0 H/s (0.00ms) @ Accel:1024 Loops:512 Thr:1 Vec:4
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 0
Rejected.........: 0
Restore.Point....: 0
Restore.Sub.#1...: Salt:0 Amplifier:0-0 Iteration:0-512
Candidates.#1....: [Copying]

ATTENTION! Read timeout in stdin mode. The password candidates input is too slow:

  • Are you sure that you are using the correct attack mode (--attack-mode or -a)?
  • Are you sure that you want to use input from standard input (stdin)?
  • If so, are you sure that the input from stdin (the pipe) is working correctly and is fast enough?

So I tried this
sudo hashcat -m 2500 -a 3 -o rockyou.txt q.hccapx -w 3
and got this.

hashcat (v5.1.0) starting...

OpenCL Platform #1: Intel(R) Corporation

  • Device #1: Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz, 6011/24046 MB allocatable, 4MCU

Hashes: 3 digests; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates

Applicable optimizers:

  • Zero-Byte
  • Single-Hash
  • Single-Salt
  • Brute-Force
  • Slow-Hash-SIMD-LOOP

Minimum password length supported by kernel: 8
Maximum password length supported by kernel: 63

Watchdog: Hardware monitoring interface not found on your system.
Watchdog: Temperature abort trigger disabled.

Skipping mask '123456' because it is smaller than the minimum password length.

Skipping mask '12345' because it is smaller than the minimum password length.

The wordlist or mask that you are using is too small.
This means that hashcat cannot use the full parallel power of your device(s).
Unless you supply more work, your cracking speed will drop.
For tips on supplying more work, see: https://hashcat.net/faq/morework

Approaching final keyspace - workload adjusted.

Session..........: hashcat
Status...........: Exhausted
Hash.Type........: WPA-EAPOL-PBKDF2
Hash.Target......: Qxxx (AP:2c:99:24:55:be:19 STA:94:27:90:09:78:a9)
Time.Started.....: Tue Oct 8 13:04:48 2019 (0 secs)
Time.Estimated...: Tue Oct 8 13:04:48 2019 (0 secs)
Guess.Mask.......: 123456789 [9]
Guess.Queue......: 3/14336792 (0.00%)
Speed.#1.........: 243 H/s (0.35ms) @ Accel:1024 Loops:512 Thr:1 Vec:4
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 1/1 (100.00%)
Rejected.........: 0/1 (0.00%)
Restore.Point....: 1/1 (100.00%)
Restore.Sub.#1...: Salt:0 Amplifier:0-1 Iteration:0-1
Candidates.#1....: 123456789 -> 123456789

The wordlist or mask that you are using is too small.
This means that hashcat cannot use the full parallel power of your device(s).
Unless you supply more work, your cracking speed will drop.
For tips on supplying more work, see: https://hashcat.net/faq/morework

Approaching final keyspace - workload adjusted.

If I run it as this,

When I check the GPU with,
lsmod | grep -i amd
I get this.

amdgpu 3522560 29
chash 16384 1 amdgpu
amd_iommu_v2 20480 1 amdgpu
gpu_sched 32768 1 amdgpu
ttm 102400 1 amdgpu
drm_kms_helper 180224 1 amdgpu
drm 483328 20 gpu_sched,drm_kms_helper,amdgpu,ttm
i2c_algo_bit 16384 1 amdgpu

Then I tried to get the GPU to run Hashcat the following two ways I get these results.

sudo DRI_PRIME=1 hashcat -m 2500 -a 0 -o rockyou.txt q.hccapx -w 3
hashcat (v5.1.0) starting...

OpenCL Platform #1: Intel(R) Corporation

  • Device #1: Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz, 6011/24046 MB allocatable, 4MCU

Hashes: 3 digests; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Rules: 1

Applicable optimizers:

  • Zero-Byte
  • Single-Hash
  • Single-Salt
  • Slow-Hash-SIMD-LOOP

Minimum password length supported by kernel: 8
Maximum password length supported by kernel: 63

Watchdog: Hardware monitoring interface not found on your system.
Watchdog: Temperature abort trigger disabled.

Starting attack in stdin mode...

Session..........: hashcat
Status...........: Running
Hash.Type........: WPA-EAPOL-PBKDF2
Hash.Target......: Qxxx (AP:2c:99:24:55:be:19 STA:94:27:90:09:78:a9)
Time.Started.....: Tue Oct 8 13:06:48 2019 (9 secs)
Time.Estimated...: Tue Oct 8 13:06:57 2019 (0 secs)
Guess.Base.......: Pipe
Speed.#1.........: 0 H/s (0.00ms) @ Accel:1024 Loops:512 Thr:1 Vec:4
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 0
Rejected.........: 0
Restore.Point....: 0
Restore.Sub.#1...: Salt:0 Amplifier:0-0 Iteration:0-512
Candidates.#1....: [Copying]

Session..........: hashcat
Status...........: Running
Hash.Type........: WPA-EAPOL-PBKDF2
Hash.Target......: Qxxx (AP:2c:99:24:55:be:19 STA:94:27:90:09:78:a9)
Time.Started.....: Tue Oct 8 13:06:48 2019 (19 secs)
Time.Estimated...: Tue Oct 8 13:07:07 2019 (0 secs)
Guess.Base.......: Pipe
Speed.#1.........: 0 H/s (0.00ms) @ Accel:1024 Loops:512 Thr:1 Vec:4
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 0
Rejected.........: 0
Restore.Point....: 0
Restore.Sub.#1...: Salt:0 Amplifier:0-0 Iteration:0-512
Candidates.#1....: [Copying]

ATTENTION! Read timeout in stdin mode. The password candidates input is too slow:

  • Are you sure that you are using the correct attack mode (--attack-mode or -a)?
  • Are you sure that you want to use input from standard input (stdin)?
  • If so, are you sure that the input from stdin (the pipe) is working correctly and is fast enough?

sudo DRI_PRIME=1 hashcat -m 2500 -a 3 -o rockyou.txt q.hccapx -w 3
hashcat (v5.1.0) starting...

OpenCL Platform #1: Intel(R) Corporation

  • Device #1: Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz, 6011/24046 MB allocatable, 4MCU

Hashes: 3 digests; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates

Applicable optimizers:

  • Zero-Byte
  • Single-Hash
  • Single-Salt
  • Brute-Force
  • Slow-Hash-SIMD-LOOP

Minimum password length supported by kernel: 8
Maximum password length supported by kernel: 63

Watchdog: Hardware monitoring interface not found on your system.
Watchdog: Temperature abort trigger disabled.

[s]tatus [p]ause [b]ypass [c]heckpoint [q]uit => s

Session..........: hashcat
Status...........: Running
Hash.Type........: WPA-EAPOL-PBKDF2
Hash.Target......: Qxxx (AP:2c:99:24:55:be:19 STA:94:27:90:09:78:a9)
Time.Started.....: Tue Oct 8 13:08:37 2019 (4 secs)
Time.Estimated...: Wed Sep 7 18:27:43 2050 (30 years, 335 days)
Guess.Mask.......: ?1?2?2?2?2?2?2?3 [8]
Guess.Charset....: -1 ?l?d?u, -2 ?l?d, -3 ?l?d*!$@_, -4 Undefined
Guess.Queue......: 1/8 (12.50%)
Speed.#1.........: 5671 H/s (89.62ms) @ Accel:1024 Loops:512 Thr:1 Vec:4
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 24576/5533380698112 (0.00%)
Rejected.........: 0/24576 (0.00%)
Restore.Point....: 0/89248075776 (0.00%)
Restore.Sub.#1...: Salt:0 Amplifier:6-7 Iteration:0-512
Candidates.#1....: 0arierin -> 0bbierin

[s]tatus [p]ause [b]ypass [c]heckpoint [q]uit =>

I can only get it to run by running,
sudo DRI_PRIME=1 hashcat -m 2500 -a 3 -o rockyou.txt q.hccapx -w 3 If you notice I have to run it backwards wordlist first then hccapx.

When I check it with,
sudo lshw -c display

I get this.

*-display
description: VGA compatible controller
product: Baffin [Radeon RX 550 640SP / RX 560/560X]
vendor: Advanced Micro Devices, Inc. [AMD/ATI]
physical id: 0
bus info: pci@0000:01:00.0
version: cf
width: 64 bits
clock: 33MHz
capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
configuration: driver=amdgpu latency=0
resources: irq:30 memory:e0000000-efffffff memory:f0000000-f01fffff ioport:e000(size=256) memory:f7e00000-f7e3ffff memory:c0000-dffff

With,
lsmod | grep -i amd

amdgpu 3522560 32
chash 16384 1 amdgpu
amd_iommu_v2 20480 1 amdgpu
gpu_sched 32768 1 amdgpu
ttm 102400 1 amdgpu
drm_kms_helper 180224 1 amdgpu
drm 483328 21 gpu_sched,drm_kms_helper,amdgpu,ttm
i2c_algo_bit 16384 1 amdgpu

These are the instructions I followed.

Installing OpenCL™ Runtimes for Intel® Processors - Option B

Go to Intel OpenCL Runtimes website and scroll down to the bottom of the page to Download Intel CPU Runtime for OpenCL Applications 18.1 for LINUX OS (64-bit only).

After downloading the OpenCL Runtimes for Intel Processors, 
cd ~/Downloads

Run 
sudo tar -xzf l_opencl_p_18.1.0.013.tgz
 to unpack the tgz file- please note, the OpenCL file version may update since the time as of this gist (ie as of this gist, the version is 18.1.0.013.)

cd l_opencl_p_18.1.0.013

Run 
sudo ./install.sh

A welcome screen is prompted- hold-down the "Enter" key until able to input select "2" for "I do NOT consent to the collection of my Information"

Hit "1"

Hit "1"

Hit "Enter" and then restart the computer.

If any additional Intel OpenCL errors are encountered after testing hashcat, go to section 'Installing OpenCL™ Runtimes for Intel® Processors - B'- if not, proceed with section "Testing Hashcat"Downloading Hashcat Binaries - Option A (Recommended)


Download the latest version of hashcat- scroll down to the bottom and download the version at the top of the table (as of this gist, the latest version is v5.1.0.7- be sure to download the "binaries" version of Ubuntu); use the 
wget
 command to download the latest version of hashcat from the hashcast website (e.g. 
wget https://hashcat.net/files/hashcat-5.1.0.7z
- be sure to 
cd
 into the Downloads folder for the sake of consistency).

Access the download-directory: 
cd ~/Downloads

If you haven't already, download p7zip: 
sudo apt install p7zip

Assuming you're still in the Downloads folder, run 
sudo p7zip -d hashcat-5.1.0.7z
 to unzip (if that command didn't work, simply right-click and extract file within the Downloads folder).

Access the unzipped hashcat folder by running 
cd hashcat-5.1.0.7z

Next run 
ls /usr/bin/ | grep -i hash

Run 
sudo cp hashcat64.bin /usr/bin/

sudo ln -s /usr/bin/hashcat64.bin /usr/bin/hashcat

sudo cp -Rv OpenCL/ /usr/bin/

sudo cp hashcat.hcstat2 /usr/bin/

sudo cp hashcat.hctune /usr/bin/

Then I run
sudo hashcat --benchmark
I get this.
hashcat (v5.1.0) starting in benchmark mode...

Benchmarking uses hand-optimized kernel code by default.
You can use it in your cracking session by setting the -O option.
Note: Using optimized kernel code limits the maximum supported password length.
To disable the optimized kernel code in benchmark mode, use the -w option.

OpenCL Platform #1: Intel(R) Corporation

  • Device #1: Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz, 6011/24046 MB allocatable, 4MCU

Benchmark relevant options:

  • --optimized-kernel-enable

Hashmode: 0 - MD5

Speed.#1.........: 158.8 MH/s (26.33ms) @ Accel:1024 Loops:1024 Thr:1 Vec:4

Hashmode: 100 - SHA1

Speed.#1.........: 117.2 MH/s (35.62ms) @ Accel:1024 Loops:1024 Thr:1 Vec:4

Hashmode: 1400 - SHA2-256

Speed.#1.........: 51439.7 kH/s (81.37ms) @ Accel:1024 Loops:1024 Thr:1 Vec:4

Hashmode: 1700 - SHA2-512

Speed.#1.........: 14678.9 kH/s (71.31ms) @ Accel:1024 Loops:256 Thr:1 Vec:2

Hashmode: 2500 - WPA-EAPOL-PBKDF2 (Iterations: 4096)

Speed.#1.........: 5451 H/s (93.49ms) @ Accel:1024 Loops:512 Thr:1 Vec:4

Hashmode: 1000 - NTLM

Speed.#1.........: 280.7 MH/s (14.49ms) @ Accel:1024 Loops:1024 Thr:1 Vec:4

Hashmode: 3000 - LM

If you look at these, I took a shot and installed Watchdog nothing changed.

sudo DRI_PRIME=1 hashcat -m 2500 -a 0 q.hccapx rockyou.txt
hashcat (v5.1.0) starting...

OpenCL Platform #1: Intel(R) Corporation

  • Device #1: Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz, 6011/24046 MB allocatable, 4MCU

Hashes: 3 digests; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Rules: 1

Applicable optimizers:

  • Zero-Byte
  • Single-Hash
  • Single-Salt
  • Slow-Hash-SIMD-LOOP

Minimum password length supported by kernel: 8
Maximum password length supported by kernel: 63

Watchdog: Hardware monitoring interface not found on your system.
Watchdog: Temperature abort trigger disabled.

Dictionary cache hit:

  • Filename..: rockyou.txt
  • Passwords.: 14344384
  • Bytes.....: 139921497
  • Keyspace..: 14344384

[s]tatus [p]ause [b]ypass [c]heckpoint [q]uit => s

Session..........: hashcat
Status...........: Running
Hash.Type........: WPA-EAPOL-PBKDF2
Hash.Target......: Qxxx (AP:2c:99:24:55:be:19 STA:94:27:90:09:78:a9)
Time.Started.....: Tue Oct 8 15:52:01 2019 (20 secs)
Time.Estimated...: Tue Oct 8 16:33:54 2019 (41 mins, 33 secs)
Guess.Base.......: File (rockyou.txt)
Guess.Queue......: 1/1 (100.00%)
Speed.#1.........: 5644 H/s (11.16ms) @ Accel:512 Loops:128 Thr:1 Vec:4
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 269258/14344384 (1.88%)
Rejected.........: 160714/269258 (59.69%)
Restore.Point....: 266920/14344384 (1.86%)
Restore.Sub.#1...: Salt:0 Amplifier:0-1 Iteration:2688-2816
Candidates.#1....: mahaffey -> ilovebacon

[s]tatus [p]ause [b]ypass [c]heckpoint [q]uit =>

If you notice sudo DRI_PRIME=1 hashcat -m 2500 -a 3 -o rockyou.txt q.hccapx -w 3 is the only one that sort of works. What I didn't put in is when it's -a 0 it says the list is to short and starts printing all the words it is excluding. When I select my GPU to run Hashcat it doesn't see the GPU as you can see from the info above. I have tried everything possible on here and the internet. I have tried Unbuntu 16.04, Unbuntu 18.04, Kali Linux 2019.3 (Rocm ruined two of Kali. It wouldn't boot after install.) Windows 10 Pro. On windows it wont load the opencl and Hashcat’s directions are no good, removeing all AMD files just causes a mess that took me half a day to fix. I just want you to understand I have been battling this for over a week before asking. I almost have it beat “I hope”. Unbuntu 18.04 is the first time I didn't get any benchmark errors and it has run semi correctly. I have installed it between the systems at least twenty times. ROCm says you have held two packages back, and no matter what I do I can't get it installed, or it just kills Kali it wont reboot after restart into anything other than Live. I had to reinstall Kali at least twice. Unbuntu already has the drivers in it, I didn't know that and somehow killed an Unbuntu operating system too, (The one and only time I could get them to install.). I spoke to MSI they where useless, MSI said that you can only install it on a Windows system that they don't even have drivers for Unbuntu or Debian. I said well I guess the drivers that are on the AMD site don't exist then. MSI really does only have the Windows driver and it is an old one . The customer service guy said that was lucky since it was old it would probably work. AMD I don’t know because they never got back to me I just received a ticket number ands that was the last I heard from them. On Kali I can get the driver to load if you go into the driver file you can add Kali to the list of systems then it loads. That didn’t kill Kali it just made the audio on the computer sound funny, same with Windows until I erased all the AMD files and reloaded them then it too sounded OK again. The hell I went through with Windows wasn’t worth the sound quality, I don’t care what it sounds like I just want it to speed up the hashes. Can you help me fix this problem ?
Robert

Please can you help me with this like I said in the post I have it pretty far along. I didn’t say this in the post but I’m finished I have reached the limits of my knowledge. Once again please help even just a little. Would be greatly appreciated. Thank you for your time, I hope to hear back from you soon. Have a great day.
Robert Dixon

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.