12-17-2019, 11:05 PM
(12-17-2019, 09:47 AM)philsmd Wrote: well, the 2 data length bounds between 7z2hashcat and hashcat are in sync... therefore if you increase one (the 7z2hashcat perl file), you would also need to increase the other one (in hashcat source code).
Changing hashcat might not be that easy, I addressed it already dozens of times in the forum and over at the 7z2hashcat and hashcat github issue tracker e.g. https://github.com/philsmd/7z2hashcat/is...ata+length+
but it's definitely possible up to some reasonable values (some dozens MB should be possible for sure, afterwards it gets even more complicated, because of hashcat's design/architecture of reading hash lines etc)
just have a look at the 7z2hashcat hashcat forum posts, hashcat issue and 7z2hashcat issue and you should be able to figure out what the problem is and how to solve it
Thank you so much, i found your article that states the following:
Quote:Modify the parsing function in src/interface.c:
Code:
https://github.com/hashcat/hashcat/blob/...e.c#L11394
the memory buffer (divided by 4 because of u32 data type) within the hook function in src/interface.c:
Code:
https://github.com/hashcat/hashcat/blob/...e.c#L14325
Increasing the value of DISPLAY_LEN_MAX_11600 (times 2 because of hex bytes) in include/interface.h:
Code:
https://github.com/hashcat/hashcat/blob/...ce.h#L1104
I have no experience or whatsoever on compiling from source. But ill find my way around this, been dealing with this for a couple of days and feels nice having some guidance.
If you have another advice or an already compiled version for windows with size "200000000" (yes this is hex, a very close aproximate to what i need) would be really appreciated.
If you have a tutorial for noobies on how to make an executable from source on windows you would also save my life.
Thanks Phil, you're the hell of a programmer.