[bug] oclHashcat-plus not printing plains

[undeath]

Hey,

I'm not sure if there already was a thread like this but I didn't find any.

I was just running a big md5 list and and realizied oclHashcat-plus somehow "forgot" to print the cracked plains into the output file.

Out of the first 14 lines there are 10 lines in format
hash::
(outfile-format=2)

This only occurred with the first cracked ones, i didn't see lines like this somewhere later in my outfile.

I remember having had such an issue some days ago too, when cracking a sha1(salt.pass) and I think it wasn't even oclHashcat-plus but oclHashcat. (but I'm not sure about this!)


Could you have a look into this, atom?


greez undeath

[Rolf]

I have a feeling you are having amd gpu.
Am I right ?

[undeath]

that's true.

[atom]

can not reproduce this locally

[rageltman]

I can confirm this with ATI 6970M using catalyst 11.11. Actually rather problematic... any known fix for this?

[atom]

since i can not reproduce it, no

[shapleigh]

I have experienced a similar problem using cudahashcat-plus64, but, in my case the incorrect results appear throughout the entire .out at random.

1be168ff837f043bde17c0314341c84271047b31:1234

2b85948590bb246968798518964ceb578892dfa0:1111

1489f923c4dca729178b3e3233458550d8dddf29:
328ab51e6ea7b55140a334b8156239218f43189f:whitesara1
d9ce264dff21de3b38533bae7592d6978d11b40e:baxxmann
a6cc26e7f22b3d6e6de0abfdc7f45636128fc5f6:helkhann
3f786850e387550fdab836ed7e6dc881de23001b:a

430bee6110f9346af26215af1f8a9521cabfbcd2:aqeyusx
a8a45476f16442d3bf8b2a8c3eb0f0c14ef2daf8umuqing

its seems to happen most when using generated.RULE from the pre-made rule files, it has occurred in both -m 0 and -m 100, also the completely blank lines are being produced by hashcat also, I did not add them.

win7 64 Nvidea gtx-120(please don't laugh to hard at my card)