hashcat Forum
Bug with Plain.Length.: display? - Printable Version

+- hashcat Forum (https://hashcat.net/forum)
+-- Forum: Deprecated; Ancient Versions (https://hashcat.net/forum/forum-46.html)
+--- Forum: Very old oclHashcat-lite Support (https://hashcat.net/forum/forum-22.html)
+--- Thread: Bug with Plain.Length.: display? (/thread-1385.html)



Bug with Plain.Length.: display? - chort - 07-16-2012

I set pw-max to 8 and the Plain.Text. seems to be 8, but the display for Plain.Length. says 16.

$ ./oclhl64 -m 2400 -n 800 -d 2 --gpu-loops 1024 --pw-max 8 HASH
oclHashcat-lite v0.10 by atom starting...

Password lengths range: 1 - 8
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 80c
Device #1: skipped by user
Device #2: Cypress, 512MB, 600Mhz, 20MCU

WARN: ADL_Overdrive5_FanSpeedInfo_Get(): -1

[s]tatus [p]ause [r]esume [q]uit => s
Status.......: Running
Hash.Target..: HASH
Hash.Type....: Cisco-PIX MD5
Time.Running.: 4 secs
Time.Left....: 28 secs
Plain.Mask...: ?1?2?2?2?2?2?2?3?3?3?3?d?d?d?d
Plain.Text...: ***aipa
Plain.Length.: 16

Progress.....: 18874368000/134960504832 (13.99%)
Speed.GPU.#1.: 4097.5M/s
HWMon.GPU.#1.: 92% Util, 73c Temp, N/A Fan
[s]tatus [p]ause [r]esume [q]uit => s
Status.......: Running
Hash.Target..: HASH
Hash.Type....: Cisco-PIX MD5
Time.Running.: 21 secs
Time.Left....: 11 secs
Plain.Mask...: ?1?2?2?2?2?2?2?3?3?3?3?d?d?d?d
Plain.Text...: ***c40p
Plain.Length.: 16

Progress.....: 86979903488/134960504832 (64.45%)Speed.GPU.#1.: 4094.5M/s
HWMon.GPU.#1.: 99% Util, 76c Temp, N/A Fan
[s]tatus [p]ause [r]esume [q]uit =>


RE: Bug with Plain.Length.: display? - atom - 07-16-2012

Bug, yeah, its because Cisco-PIX MD5 hashes are zero padded to length 16. I will try to fix it when I have some spare time but its just a display bug.


RE: Bug with Plain.Length.: display? - chort - 07-17-2012

Ahh, I was wondering if it was padded. I should have looked that up.

On the same hash I was running -plus-0.09b and I kept getting weird characters after the hash in the status display, but I guess that's a different issue.