V3.00 showing wrong password

[kiara]

first of all hi , i've been reading quiet alot in the forum but never register but now that i have an issue its time to post ;D,

so here the thing
in cudahashcat on a 2.01 the password as been found with the following command

Code:

sudo ./cudaHashcat64.bin pro -a 3 -m 1500 --custom-charset1=?l?d?u --increment --increment-min=1 --increment-min=8 ?1?1?1?1?1?1?1?1

after cracking the hash lets say the password is 1001miaa i've try hashcat 3 to test it out.
since i already knew whats the password was so i changed the request to this

 sudo ./hashcat64.bin --opencl-device-type 2 pro.txt -m 1500 -a 3 ?d?d?d?d?l?l?l?l

when i did saw instead of showing me 1001miaa it showed me 3001miaa, so i did another test, instead of ?d i put the char 1

sudo ./hashcat64.bin --opencl-device-type 2 pro.txt --custom-charset1=1 -m 1500 -a 3 ?1?d?d?d?l?l?l?l

the password on this one was 1312miaa

and another one

sudo ./hashcat64.bin --opencl-device-type 2 pro.txt --custom-charset1=124 -m 1500 -a 3 ?1?d?d?d?l?l?l?l

the pass was 1311miaa, anyway u get the point, the password was not recover, with V3.00.

perhaps i am doing somthing wrong but.. i dont see what.

[atom]

I can reproduce this locally. If you can, please create an issue for it on github so it's not forgotten

root@ht:~/hashcat# ./hashcat -m 1500 hjylVp0MsGLU. -a 3 ?d?d?d?d?l?l?l?l -w 3 --potfile-disable
hashcat (v3.00-beta-148-g063abab+) starting...

Device #1: Graphics Device, 2028/8112 MB allocatable, 20MCU
Device #2: Graphics Device, 2028/8113 MB allocatable, 20MCU
Device #3: pthread-AMD FX(tm)-6100 Six-Core Processor, skipped

Hashes: 1 hashes; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Applicable Optimizers:
* Zero-Byte
* Precompute-Final-Permutation
* Not-Iterated
* Single-Hash
* Single-Salt
* Brute-Force
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger disabled

hjylVp0MsGLU.:3001miaa

Session.Name...: hashcat
Status.........: Cracked
Input.Mode.....: Mask (?d?d?d?d?l?l?l?l) [8]
Hash.Target....: hjylVp0MsGLU.
Hash.Type......: descrypt, DES(Unix), Traditional DES
Time.Started...: Thu Jun 9 17:50:36 2016 (1 sec)
Speed.Dev.#1...: 878.5 MH/s (95.84ms)
Speed.Dev.#2...: 883.6 MH/s (96.75ms)
Speed.Dev.#*...: 1762.1 MH/s
Recovered......: 1/1 (100.00%) Digests, 1/1 (100.00%) Salts
Progress.......: 2553600000/4569760000 (55.88%)
Rejected.......: 0/2553600000 (0.00%)
Restore.Point..: 2383360/4569760 (52.16%)

Started: Thu Jun 9 17:50:36 2016
Stopped: Thu Jun 9 17:50:45 2016

[atom]

Should be fixed with latest beta. Thanks for reporting

[kiara]

Should be fixed with latest beta. Thanks for reporting

did u reproduce the issue on ur rig to?


idk how to creat an issue on github sry

3001miaa  was just an example, the password is actualy something else. (does it matter?) i can give u all the detail on pm if u want, i understand putting a hash on the forum is not allowed (unless its ok for the test..)

btw
how can we ensure that every singel algorithim is working properly so we wont waste hours,days,week,month cracking hashes that will give us a wrong password :o

[atom]

Before we do the release version we run the unit tests, automated tests that crack random passwords for each algorithm. But you are using a beta version, those are not run through the unit tests, so you have to expect errors.

Also I fixed the bug, you didn't report back if it is fixed. Please do that

[kiara]

Before we do the release version we run the unit tests, automated tests that crack random passwords for each algorithm. But you are using a beta version, those are not run through the unit tests, so you have to expect errors.

Also I fixed the bug, you didn't report back if it is fixed. Please do that

its working now
gj!