Windows7 64-bit, nVidia, 304,79 beta, oclHashcat-plus-0.09b70.
Starting with previous bugs:
-m3100: Fixed! Great job as always!
-m3000:
.... -a0: This is weird, when I tried to stdin a single plain it cracked the pass, stding the whole dict did NOT work.
Please try with a dict at the end of your command OR with a "< dict".
Here's an example:
.... -a6: My theory says: Whenever the FULL 7 character long plain is present in your -a6 dictionary, hashcat wouldn't mind adding ANY char at the end of the cracked plain. E.g.:
Testing this in deep raised another bug, I believe it's closely related to the one mentioned above:
Going to post about speed in a short time.
10 MD5 and 10 vBulletin 4:
oclHashcat-plus-0.08
hc64p -n320 --gpu-loops=512 -a3 -1 ?l?u?d?s --runtime=60 10md5.hash ?1?1?1?1?1?1?1?1
Speed........: 227.6M c/s Real, 227.7M c/s GPU
hc64p -n320 -m2711 -a3 -1 ?l?u?d?s --runtime=60 10vbu4.hash ?1?1?1?1?1?1?1?1
Speed........: 53132.3k c/s Real, 53142.0k c/s GPU
oclHashcat-plus-0.09b71
hc64p -n320 --gpu-loops=512 -a3 --bf-min=8 --runtime=60 10md5.hash ?a?a?a?a?a?a?a?a
Speed........: 263.5M c/s Real, 264.0M c/s GPU
hc64p -n320 -m2711 -a3 --bf-min=8 --runtime=60 10vbu4.hash ?a?a?a?a?a?a?a?a
Speed........: 63604.3k c/s Real, 63728.1k c/s GPU
Already tried 5k IPB hashes, the results were in favor of the new version.
Starting with previous bugs:
-m3100: Fixed! Great job as always!
-m3000:
.... -a0: This is weird, when I tried to stdin a single plain it cracked the pass, stding the whole dict did NOT work.
Please try with a dict at the end of your command OR with a "< dict".
Here's an example:
Code:
44EFCE164AB921CA:123456
echo 123456 > dict
hc64p -m3000 44EFCE164AB921CA dict
NOT FOUND!
hc64p -m3000 44EFCE164AB921CA < dict
NOT FOUND!
echo -n 123456 | hc64p -m3000 44EFCE164AB921CA
FOUND!.... -a6: My theory says: Whenever the FULL 7 character long plain is present in your -a6 dictionary, hashcat wouldn't mind adding ANY char at the end of the cracked plain. E.g.:
Code:
E3493F9DD1EB6F82:______7
echo ______7 > dict // notice the full plain
hc64p -m3000 -a6 E3493F9DD1EB6F82 dict 0
e3493f9dd1eb6f82:______70
Status.......: Cracked
hc64p -m3000 -a6 E3493F9DD1EB6F82 dict X
e3493f9dd1eb6f82:______7X
Status.......: Cracked
hc64p -m3000 -a6 E3493F9DD1EB6F82 dict ~
e3493f9dd1eb6f82:______7~
Status.......: CrackedTesting this in deep raised another bug, I believe it's closely related to the one mentioned above:
Code:
E3493F9DD1EB6F82:______7
echo ______ > dict // missing the last char only
hc64p -m3000 -a6 E3493F9DD1EB6F82 dict ?d
Status.......: Exhausted
Input.Base...: File (dict)
Input.Mod....: Mask (?d)
Exhausted!Going to post about speed in a short time.
atom Wrote: how many hashes did you use for testing?1mfakemd5.hash = 1 million.
atom Wrote: I am back at 304.x and CUDA 5.0 RC but still it has not the speed of 0.081 on high number of hashes. On low number of hashes, new version is faster. Can you verify?I can verify, see below:
10 MD5 and 10 vBulletin 4:
oclHashcat-plus-0.08
hc64p -n320 --gpu-loops=512 -a3 -1 ?l?u?d?s --runtime=60 10md5.hash ?1?1?1?1?1?1?1?1
Speed........: 227.6M c/s Real, 227.7M c/s GPU
hc64p -n320 -m2711 -a3 -1 ?l?u?d?s --runtime=60 10vbu4.hash ?1?1?1?1?1?1?1?1
Speed........: 53132.3k c/s Real, 53142.0k c/s GPU
oclHashcat-plus-0.09b71
hc64p -n320 --gpu-loops=512 -a3 --bf-min=8 --runtime=60 10md5.hash ?a?a?a?a?a?a?a?a
Speed........: 263.5M c/s Real, 264.0M c/s GPU
hc64p -n320 -m2711 -a3 --bf-min=8 --runtime=60 10vbu4.hash ?a?a?a?a?a?a?a?a
Speed........: 63604.3k c/s Real, 63728.1k c/s GPU
Already tried 5k IPB hashes, the results were in favor of the new version.