02-18-2018, 01:31 AM
(02-17-2018, 01:53 PM)philsmd Wrote: See this issue https://github.com/hashcat/hashcat/issues/112 . I think it might be possible to just truncate the long encrypted data for -m 12700 = Blockchain, My Wallet .
You could for instance try to make it only 288 bytes long and therefore use $blockchain$288$ and also truncate the data to 576 hex chars (which corresponds to 576 / 2 = 288 bytes).
Without an example for which we for sure know the password I can't tell for sure.
The first 32 chars are the salt and after that we have the raw data.
for -m 12700 it should be possible to use a truncated version of the raw data and still be able to verify if the decryption reveals known plaintext bytes.
Maybe you can provide examples with password (test accounts) on the github issue or send them to me in a PM (you are not allowed to post hashes on the forums without a moderator/admin requesting it, don't copy-paste hashes into public available forum posts).
your example also does not seem to contain only random data. There is way to many zero-bytes etc. Did you edit this hash or is this the unmodified version?
It doesn't seem to have a valid random salt and random data etc.
I have a wallet file, I just extracted the hash.
How do I convert 288 bytes long and consequently use $ blockchain $ 288 $
I dont know