03-26-2015, 11:50 AM
This trac ticket https://hashcat.net/trac/ticket/539 seems to be related to your question.
The main reasons it wasn't implemented yet, was that the full details about the maximum length devs should support for each "part" is not clear.
Remember, MD5 works "block-wise", hence if the lengths of parts are limited (e.g. < 55) devs could optimize this algorithm, otherwise it might get quickly relatively slower.
Currently the algorithm is not yet supported, but maybe you can share some example hashes, more detailed information etc on the trac ticket mentioned above and it may get implemented sooner/prioritized.
Thx
The main reasons it wasn't implemented yet, was that the full details about the maximum length devs should support for each "part" is not clear.
Remember, MD5 works "block-wise", hence if the lengths of parts are limited (e.g. < 55) devs could optimize this algorithm, otherwise it might get quickly relatively slower.
Currently the algorithm is not yet supported, but maybe you can share some example hashes, more detailed information etc on the trac ticket mentioned above and it may get implemented sooner/prioritized.
Thx