New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wrong plaintext reported, kali x32 virtualized #1709

Open
deargle opened this Issue Oct 2, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@deargle

deargle commented Oct 2, 2018

Replicated on any variant of 2018.9 virtualized i686 Kali, including kali live cd. Issue not present on x64. It appears that the first password from the "candidates" list is always reported as the plaintext. For example, in the below demo, "wrong_password" is reported when the crack for "Password1" is found in a dict file comprised of only "wrong_password" and "Password1". If "Password1" is listed first in the dict file, it is reported instead of "wrong_password".

root@kali:~# uname -a
Linux kali 4.18.0-kali1-686-pae #1 SMP Debian 4.18.6-1kali1 (2018-09-10) i686 GNU/Linux
root@kali:~# echo -n "Password1" | md5sum
2ac9cb7dc02b3c0083eb70898e549b63  -
root@kali:~# echo "wrong_password" > custom_dict.txt
root@kali:~# echo "Password1" >> custom_dict.txt 
root@kali:~# hashcat --force -a 0 -m 0 2ac9cb7dc02b3c0083eb70898e549b63 custom_dict.txt
hashcat (v4.2.1) starting...

OpenCL Platform #1: The pocl project
====================================
* Device #1: pthread-Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz, 512/1512 MB allocatable, 2MCU

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
* Early-Skip
* Not-Salted
* Not-Iterated
* Single-Hash
* Single-Salt
* Raw-Hash

Minimum password length supported by kernel: 0
Maximum password length supported by kernel: 256

ATTENTION! Pure (unoptimized) OpenCL kernels selected.
This enables cracking passwords and salts > length 32 but for the price of drastically reduced performance.
If you want to switch to optimized OpenCL kernels, append -O to your commandline.

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

* Device #1: build_opts '-cl-std=CL1.2 -I OpenCL -I /usr/share/hashcat/OpenCL -D VENDOR_ID=64 -D CUDA_ARCH=0 -D AMD_ROCM=0 -D VECT_SIZE=8 -D DEVICE_TYPE=2 -D DGST_R0=0 -D DGST_R1=3 -D DGST_R2=2 -D DGST_R3=1 -D DGST_ELEM=4 -D KERN_TYPE=0 -D _unroll'
Dictionary cache built:
* Filename..: custom_dict.txt
* Passwords.: 2
* Bytes.....: 25
* Keyspace..: 2
* 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.  

2ac9cb7dc02b3c0083eb70898e549b63:wrong_password  
                                                 
Session..........: hashcat
Status...........: Cracked
Hash.Type........: MD5
Hash.Target......: 2ac9cb7dc02b3c0083eb70898e549b63
Time.Started.....: Tue Oct  2 11:37:07 2018 (0 secs)
Time.Estimated...: Tue Oct  2 11:37:07 2018 (0 secs)
Guess.Base.......: File (custom_dict.txt)
Guess.Queue......: 1/1 (100.00%)
Speed.Dev.#1.....:     3635 H/s (0.01ms) @ Accel:1024 Loops:1 Thr:1 Vec:8
Recovered........: 1/1 (100.00%) Digests, 1/1 (100.00%) Salts
Progress.........: 2/2 (100.00%)
Rejected.........: 0/2 (0.00%)
Restore.Point....: 0/2 (0.00%)
Candidates.#1....: wrong_password -> Password1
HWMon.Dev.#1.....: N/A

Started: Tue Oct  2 11:37:07 2018
Stopped: Tue Oct  2 11:37:08 2018
@philsmd

This comment has been minimized.

Show comment
Hide comment
@philsmd

philsmd Oct 4, 2018

Member

Could you please test with the recommended proprietary driver from intel instead of the experimental (open source) pocl driver? I'm pretty sure it's a driver problem.
recommended driver versions: https://hashcat.net/hashcat (yeah, I know pocl is listed there too, but it's not recommended, see the dozens of bug reports on the hashcat forum and on github... the driver is not really production ready for OpenCL tasks)

Member

philsmd commented Oct 4, 2018

Could you please test with the recommended proprietary driver from intel instead of the experimental (open source) pocl driver? I'm pretty sure it's a driver problem.
recommended driver versions: https://hashcat.net/hashcat (yeah, I know pocl is listed there too, but it's not recommended, see the dozens of bug reports on the hashcat forum and on github... the driver is not really production ready for OpenCL tasks)

@deargle

This comment has been minimized.

Show comment
Hide comment
@deargle

deargle Oct 4, 2018

I'm a noob with manual driver install but I'll give it a shot. Following this: https://github.com/intel/compute-runtime/blob/master/documentation/BUILD_Ubuntu.md

deargle commented Oct 4, 2018

I'm a noob with manual driver install but I'll give it a shot. Following this: https://github.com/intel/compute-runtime/blob/master/documentation/BUILD_Ubuntu.md

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment