Is it a md5 colision ?

[philsmd]

Mystery solved!
Try:

Code:

echo -en "elec@\00"|md5sum 9a214e678ed4e501d1576326ce84b41c *-

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.

Code:

$ cat 2rules.rule : '9 $ cat dict.txt philsmd@ $ cat md5.txt # X MASKED 8e640164e8e1XXXX38d9ffb03b451XXX 5b370275e1bbXXXX24f89024bd8f5XXX $ cudaHashcat-plus32.exe md5.txt dict.txt -r 2rules.rule cudaHashcat-plus v0.15 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 set to 90c Watchdog: Temperature retain trigger set to 80c Device #1: GeForce GTX 580, 3072MB, 1682Mhz, 16MCU Device #1: Kernel ./kernels/4318/m0000_a0.sm_20.32.ptx Generated dictionary stats for dict.txt: 9 bytes, 1 words, 2 keyspace NOTE: autotuned --gpu-accel from 80 to 1 8e640164e8e1XXXX38d9ffb03b451XXX:philsmd@ 5b370275e1bbXXXX24f89024bd8f5XXX:philsmd@ Session.Name...: cudaHashcat-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 12:24:32 2013 (2 secs) 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%) HWMon.GPU.#1...: 0% Util, 53c Temp, 1830rpm Fan Started: Sun Apr 14 12:24:32 2013 Stopped: Sun Apr 14 12:24:35 2013

Note: the second one was generated via:

Code:

echo -en "philsmd@\00"|md5sum