Output Bug Report

[oxaners]

A bug has come to my attention during my recent testing. It is limited to -plus and seems to work fine on -lite (haven't tested CPU).

Basically, when using a hex charset and including x00, the plaintext output, in hex, will be truncated by dropping everything after and including the first x00. I have a couple sample outputs below:


oclHashcat-plus64.exe -m 100 -a 3 --force --outfile-format=5 --hex-charset -1 000102030405060708 cbe4c12958ab208cba48401c53ecd9ff63f76e68 ?1?1?1?1?1
oclHashcat-plus v0.08 by atom starting...

cbe4c12958ab208cba48401c53ecd9ff63f76e68:0603

Status.......: Cracked
Input.Mode...: Mask (?1?1?1?1?1)
Hash.Target..: cbe4c12958ab208cba48401c53ecd9ff63f76e68
Hash.Type....: SHA1



The output should look like the one from -lite:



oclHashcat-lite64.exe -m 100 --outfile-format=5 --hex-charset -1 000102030405060708 cbe4c12958ab208cba48401c53ecd9ff63f76e68 ?1?1?1?1?1
oclHashcat-lite v0.10 by atom starting...

cbe4c12958ab208cba48401c53ecd9ff63f76e68:0603000102

Status.......: Cracked
Hash.Target..: cbe4c12958ab208cba48401c53ecd9ff63f76e68
Hash.Type....: SHA1
Plain.Mask...: ?1?1?1?1?1

[atom]

Looks interessting. Someone can reproduce I am a bit busy coding sun-md5.

[oxaners]

Just checking to see if anyone has had a chance to reproduce this? Currently my workaround is to just send the -plus cracked hash to -lite if it's found, with the proper mask and re-crack

[M@LIK]

I believe it's fixed I reported something very similar.

[atom]

Done with oclHashcat-plus v0.09: https://hashcat.net/forum/thread-1541.html

Thread closed