Setting up Hashcat for CPU Hacking on Debian
Hashcat for CPU hacking turned out to be an adventure that almost failed, this is a quick post of the steps needed as a referece if I need to repeat this process again.
One could setup run John The Ripper (simpler setup) however I decided to use Hashcat as it's GPU cracking is faster compared to JtR and so down the line I won't have to re-learn.
- Install Hashcat direclty https://hashcat.net/hashcat/
- Install AMD OpenCL CPU package, it has been discounteued but you can get it here.
- tar xvfj AMD-APP-SDKInstaller-v188.8.131.52-GA-linux64.tar.bz2
- ./hashcat64.bin -b --force
If the above clinfo or hashccat64.bin fail see https://askubuntu.com/q/821341, and confirm `/etc/ld.so.conf.d/AMDAPPSDK.conf` is proper, and also you might need to set your LD_LIBRARY_PATH and LIBRARY_PATH, see https://hashcat.net/forum/thread-7190.html.
Run `./hashcat64.bin --benchmark --force`
If everything worked you should see the below, now you might want to contribute those cycles to the Distributed WPA PSK auditor project. If this post helped you do comment of follow on twitter @danielsokolow.
root@tardis:/usr/local/hashcat-5.1.0# ./hashcat64.bin --benchmark --force 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: Advanced Micro Devices, Inc. ================================================ * Device #1: Pentium(R) Dual-Core CPU E5400 @ 2.70GHz, 2048/3419 MB allocatable, 2MCU Benchmark relevant options: =========================== * --force * --optimized-kernel-enable Hashmode: 0 - MD5 Speed.#1.........: 55405.8 kH/s (37.24ms) @ Accel:1024 Loops:1024 Thr:1 Vec:4 Hashmode: 100 - SHA1 Speed.#1.........: 30290.6 kH/s (68.63ms) @ Accel:1024 Loops:1024 Thr:1 Vec:4 Hashmode: 1400 - SHA2-256