(07-15-2018, 05:45 PM)undeath Wrote: What command are you running to crack the example hash and what output do you receive?
I use the command "hashcat64.exe -m 3200 hash.txt pass.txt"
where in the hash.txt there is : $2a$05$LhayLxezLhK1LhWvKxCyLOj0j1u.Kj0jZ0pEmm134uzrQlFvQJLF6 (found in the wiki page)
and in pass.txt there is the word "hashcat", selected the encode UTF-8 with notepad ( no bom) ,this is the output:
hashcat64.exe -m 3200 hash.txt pass.txt
hashcat (v4.1.0) starting...
* Device #1: Intel's OpenCL runtime (GPU only) is currently broken.
We are waiting for updated OpenCL drivers from Intel.
You can use --force to override, but do not report related errors.
* Device #4: Not a native Intel OpenCL runtime. Expect massive speed loss.
You can use --force to override, but do not report related errors.
ADL_Overdrive_Caps(): -8
ADL_Overdrive_Caps(): -8
ADL_Overdrive6_TargetTemperatureData_Get(): -8
OpenCL Platform #1: Intel(R) Corporation
========================================
* Device #1: Intel(R) UHD Graphics 620, skipped.
* Device #2: Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz, skipped.
OpenCL Platform #2: Advanced Micro Devices, Inc.
================================================
* Device #3: Iceland, 3264/4096 MB allocatable, 6MCU
* Device #4: Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz, skipped.
Hashes: 1 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
Minimum password length supported by kernel: 0
Maximum password length supported by kernel: 72
Watchdog: Temperature abort trigger set to 90c
* Device #3: ATTENTION! OpenCL kernel self-test failed.
Your device driver installation is probably broken.
See also: https://hashcat.net/faq/wrongdriver
Dictionary cache built:
* Filename..: pass.txt
* Passwords.: 1
* Bytes.....: 8
* Keyspace..: 1
* Runtime...: 0 secs
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........: bcrypt $2*$, Blowfish (Unix)
Hash.Target......: $2a$05$LhayLxezLhK1LhWvKxCyLOj0j1u.Kj0jZ0pEmm134uzr...vQJLF6 <-- (from hashcat wiki)
Time.Started.....: Mon Jul 16 14:33:44 2018 (0 secs)
Time.Estimated...: Mon Jul 16 14:33:44 2018 (0 secs)
Guess.Base.......: File (pass.txt)
Guess.Queue......: 1/1 (100.00%)
Speed.Dev.#3.....: 9 H/s (2.75ms) @ Accel:4 Loops:1 Thr:8 Vec:1
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%)
Candidates.#3....: hashcat -> hashcat
HWMon.Dev.#3.....: Temp: 49c Fan: 0% Util: 8% Core:1024MHz Mem:1125MHz Bus:4
Started: Mon Jul 16 14:33:31 2018
Stopped: Mon Jul 16 14:33:46 2018
C:\Users\********\hashcat-4.1.0>
i've installed this version of sdk amd : AMD-APP-SDKInstaller-v3.0.130.135
seems that every driver that i have seems not to work.., starting from intel i5 8250u, UHD intel 620 and then the Radeon. While i was testing the differents types of hash at some point hashcat could crack it correctly bcrypt, but after retyping the command it stop working. Then i just moved to different type of driver and came here. To notice that i can crack the other hash, and i'm having problems in ubuntu 18 too