08-21-2015, 02:22 PM
There is no fixed size for the output of 7z2hashcat.pl. There are just some upper and lower length limits (i.e. the minimum info/bytes required and the maximum number of bytes of the blob that oclHashcat could verify *on GPU*).
It depends on many factors, such as if the file has encrypted header (file list), how many files there are within the .7z file, if checksum/crc32 check is possible or not (this is not always the case and furthermore is prone to collisions)...
The details can be checked by looking at the source code of 7z2hashcat.pl or (even better but also more "complicated") at the .7z file format description.
In short: there is no such thing like "target size of the output of 7z2hashcat.pl" because oclHashcat must have "just enough" information to be able to verify the data given a password candidate.
It depends on many factors, such as if the file has encrypted header (file list), how many files there are within the .7z file, if checksum/crc32 check is possible or not (this is not always the case and furthermore is prone to collisions)...
The details can be checked by looking at the source code of 7z2hashcat.pl or (even better but also more "complicated") at the .7z file format description.
In short: there is no such thing like "target size of the output of 7z2hashcat.pl" because oclHashcat must have "just enough" information to be able to verify the data given a password candidate.