Skip to main content

CPU Basd Hashcat Cracking

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.

I've have tried the Intel OpenCL 5.0 and 18.1 runtimes but they are not supported on our CPU Pentium(R) Dual-Core CPU E5400

  • Install Hashcat direclty
  • Install AMD OpenCL CPU package, it has been discounteued but you can get it here.
  • tar xvfj AMD-APP-SDKInstaller-v3.0.130.136-GA-linux64.tar.bz2
  • ./
  • ./clinfo
  • ./hashcat64.bin -b --force

If the above clinfo or hashccat64.bin fail see, and confirm `/etc/` is proper, and also you might need to set your LD_LIBRARY_PATH and LIBRARY_PATH, see

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


Popular posts from this blog

Duplicate value found: duplicates value on record with id: <unknown>.

System.DmlException: Insert failed. First exception on row 0; first error: DUPLICATE_VALUE, duplicate value found: <unknown> duplicates value on record with id: <unknown>. The above error is triggered in the database layer and caused by a trigger or workflow outside of your main code of block that is bubbling this exception. This is rather difficult to track down especially if you are unfamiliar with the code, I am sharing my procedure in the hopes this saves you time - if you find this helpful drop me a line or follow me on twitter @danielsokolows . This error is caused by unique field constraint on the object, so the first step is to examine the object and locate the API names of all unique fieds. You can do this through SF direclty 'Setup < Customize &lt <object being inserted> &lt Fields' or by downloading the `src/objects` metadata information and searching for <unique> ; I preffer the latter and actually download ALL matadata i

Softeher 'Error occurred. (Error code: 2)' sollution

Protocol error occurred. Error was returned from the destination server. The Softether server by default to run on port 443 , if you server also hosts normal https then 443 is already taken and so Softether can't bind to it. When you run `vpncmd` it attempts to connect, find an active port, but of course fails with 'Protocol error occurred. Error was returned from the destination server.' because it's not actually connecting to the vpn server. By default Softether also listens on 992 , 1194 , and 5555 so the sollution is to modify specify `localhost:5555` when executing the `vpncmnd`. If this has helped you feel free to comment or follow me on twitter @danielsokolows .

How to child proof a fireplace

DIY - Do it yourself fireplace child guard Our wonderful 8.5 month old Sofia has become a crawling race car with an untamed thirst for exploration. And so with the cold nights approaching we needed to child proof the fireplace. This however proved to be more difficult than would reasonably expect, I've checked the local Toys "R" Us, Walmart, and even a Canadian Tire with no success for a ready to use product. Internet search was more fruitful and returned a few online stores one could order from, however in all honestly they didn't look too sturdy to me. So I build my own relatively quickly and inexpensively. Materials needed is a privacy plastic lattice - the smallest hole pattern - a few screws and anchors; tools needed are a drill, and a handsaw if you don't have the lattice cut at the store - that’s it. The construction consits of screwing the lattice into the wall and the final product is easiest explained through following pictures.