hashcat Forum

Hi,

Quote:md5("elec@") = 7863783c727bc742d503f232f277e327

But hashcat find me :

Quote:9a214e678ed4e501d1576326ce84b41c:elec@

What is it ?!

Note for me:


Maybe you're using an old version?

Interesting behaviour !

md5.txt contains :

Quote:9a214e678ed4e501d1576326ce84b41c
7863783c727bc742d503f232f277e327

dict.txt contains :

Quote:elec@

Quote:>oclHashcat-plus64.exe md5.txt dict.txt

oclHashcat-plus v0.14 by atom starting...
...
7863783c727bc742d503f232f277e327:elec@
...
Recovered......: 1/2 (50.00%) Digests, 0/1 (0.00%) Salts

OK.

When adding rules file :

Quote:>oclHashcat-plus64.exe md5.txt dict.txt -r rules.rule
...
9a214e678ed4e501d1576326ce84b41c:elec@
7863783c727bc742d503f232f277e327:elec@
...
Recovered......: 2/2 (100.00%) Digests, 1/1 (100.00%) Salts

I guess there is a bug regarding to the rules file ?

@atom : if you confirm the bug I'll send you my rules file.

also not for me

(04-13-2013, 08:03 PM)eljolot Wrote: [ -> ]also not for me

You do not have my rules file !

Set --outfile-format=7 (or whatever the hashcat CLI version of that argument is) and see if the hex versions of the passwords are identical; perhaps there's a nonprintable character in one or the other of them. Alternately, perhaps one of the characters isn't what it appears - some non-English speaking countries have a habit of high ASCII 1337 speak.

The 78... is the basic "elec@" md5 value.

outfile-format=7 gives :

9a214e678ed4e501d1576326ce84b41c:elec@:656c656340
7863783c727bc742d503f232f277e327:elec@:656c656340

I would suggest you reduce your rule file to the bare minimum needed to reproduce this behaviour and post the few lines here.
As far as I understood, it could be a "bug" regarding the rules !?

I did it.
Here is the rule file that cause this bug (2 rules) :

Quote::
'6

So first one does nothing, second one truncates word at position (here) 6.

Quote:>oclHashcat-plus64.exe md5.txt dict.txt -r 2rules.rule
oclHashcat-plus v0.14 by atom starting...

Hashes: 2 total, 1 unique salts, 2 unique digests
Bitmaps: 8 bits, 256 entries, 0x000000ff mask, 1024 bytes
Rules: 2
Workload: 256 loops, 80 accel
Watchdog: Temperature abort trigger disabled
Watchdog: Temperature retain trigger disabled
Device #1: Cypress, 1024MB, 850Mhz, 20MCU
Device #1: Kernel oclHashcat-plus-0.14/kernels/4098/m0000_a0.Cypress_1084.4_1084.4 (VM).kernel (1109768 bytes)

Cache-hit dictionary stats dict.txt: 5 bytes, 1 words, 2 keyspace

NOTE: autotuned --gpu-accel from 80 to 8

9a214e678ed4e501d1576326ce84b41c:elec@
7863783c727bc742d503f232f277e327:elec@

Session.Name...: oclHashcat-plus
Status.........: Cracked
Rules.Type.....: File (2rules.rule)
Input.Mode.....: File (dict.txt)
Hash.Target....: File (md5.txt)
Hash.Type......: MD5
Time.Started...: Sun Apr 14 11:36:52 2013 (1 sec)
Speed.GPU.#1...: 0/s
Recovered......: 2/2 (100.00%) Digests, 1/1 (100.00%) Salts
Progress.......: 2/2 (100.00%)
Rejected.......: 0/2 (0.00%)

Mystery solved!
Try:

So the string terminator \0 is included into the "search string" when the 'x rule has a length of strlen(dict_entry)+1 e.g. strlen(elec@)+1 == 6 in your case.


Note: the second one was generated via: