12-03-2017, 09:52 AM
(This post was last modified: 12-03-2017, 10:13 AM by nazgulnarsil.)
Used 7z2hashcat, then loaded up hashcat and:
Hashfile 'hashuni.txt' on line 1 (▒▒$): Line-length exception
Parsing Hashes: 0/1 (0.00%)...No hashes loaded
In unicode save format.
Saved in UTF8 in case it was an encoding problem and it just overruns the text area and returns no hashes loaded without me being able to see the error message.
any ideas? The hash looks well formatted AFAICT. The only suspcious thing is the - in the header:
$7z$1$19$0$$8$b9bbba35e180b4e30000000000000000$-914293439$
Also the encrypted data following the header is very long, thousands of characters. Judging from the example hashes page this might not be right? It is just the output from 7z2hashcat, could the error be in that step? Could the original file be corrupted?
I also see on 7z2hashcat
1 means that the data must be decompressed using the LZMA1 decompressor
is there an additional intermediate step I am missing?
However I saw this:
"In addition to some bug fixes, they now also support decompressing LZMA1/LZMA data streams. The header decompression problem in 7z2hashcat.pl seems to be fixed too. Currently there are no further known problems" from the 7z2hashcat thread so I'm thinking it must be something else.
any help or thoughts much appreciated.
Cheers
Hashfile 'hashuni.txt' on line 1 (▒▒$): Line-length exception
Parsing Hashes: 0/1 (0.00%)...No hashes loaded
In unicode save format.
Saved in UTF8 in case it was an encoding problem and it just overruns the text area and returns no hashes loaded without me being able to see the error message.
any ideas? The hash looks well formatted AFAICT. The only suspcious thing is the - in the header:
$7z$1$19$0$$8$b9bbba35e180b4e30000000000000000$-914293439$
Also the encrypted data following the header is very long, thousands of characters. Judging from the example hashes page this might not be right? It is just the output from 7z2hashcat, could the error be in that step? Could the original file be corrupted?
I also see on 7z2hashcat
1 means that the data must be decompressed using the LZMA1 decompressor
is there an additional intermediate step I am missing?
However I saw this:
"In addition to some bug fixes, they now also support decompressing LZMA1/LZMA data streams. The header decompression problem in 7z2hashcat.pl seems to be fixed too. Currently there are no further known problems" from the 7z2hashcat thread so I'm thinking it must be something else.
any help or thoughts much appreciated.
Cheers