06-02-2013, 06:47 AM
Perfect, thx Waffle for these details.
It is just a pity that I/we weren't aware of these speed-truncation mechanism, unfortunatelly I think nobody documented this behaviour and why it can't be avoided neither here http://hashcat.net/forum/thread-2228.html nor here https://hashcat.net/trac/ticket/154 before.
So your last post seems to be *THE* valid answer and I suggest if nobody has valid arguments against it that we close https://hashcat.net/trac/ticket/154 as unresolvable AND/OR that it is *now* a output-problem only (because those \00 bytes sometimes need to be there to avoid performance issues) AND state there (again) that while those unexpected null bytes cannot easily be fixed a correct output format should allow to detect them.
Thx Waffle for this good points
It is just a pity that I/we weren't aware of these speed-truncation mechanism, unfortunatelly I think nobody documented this behaviour and why it can't be avoided neither here http://hashcat.net/forum/thread-2228.html nor here https://hashcat.net/trac/ticket/154 before.
So your last post seems to be *THE* valid answer and I suggest if nobody has valid arguments against it that we close https://hashcat.net/trac/ticket/154 as unresolvable AND/OR that it is *now* a output-problem only (because those \00 bytes sometimes need to be there to avoid performance issues) AND state there (again) that while those unexpected null bytes cannot easily be fixed a correct output format should allow to detect them.
Thx Waffle for this good points