05-12-2018, 09:45 PM
apparently there are different schemes used for encrypting blockchain v1 wallets, according to this post: https://bitcointalk.org/index.php?topic=...sg11105755
I'm not sure if the BCM makes any difference for hashcat since only the first AES block appears to ever be decrypted and the padding should not cause any difference but some wallets use 10 iterations and others only 1. From looking at the kernel source I couldn't find a loop involving 10, hence I assume only wallets with 1 pbkdf2 iteration are supported in hashcat.
That said, if all the above is correct and your wallet was only using 1 iteration (apparently there is no way to figure out from the encrypted data) you should be able to simply shorten the hash.
The number after $blockchain$ holds the number of bytes of data. Hence you can change it to 288 and truncate the following hex data after 288*2 = 576 characters.
I'm not sure if the BCM makes any difference for hashcat since only the first AES block appears to ever be decrypted and the padding should not cause any difference but some wallets use 10 iterations and others only 1. From looking at the kernel source I couldn't find a loop involving 10, hence I assume only wallets with 1 pbkdf2 iteration are supported in hashcat.
That said, if all the above is correct and your wallet was only using 1 iteration (apparently there is no way to figure out from the encrypted data) you should be able to simply shorten the hash.
The number after $blockchain$ holds the number of bytes of data. Hence you can change it to 288 and truncate the following hex data after 288*2 = 576 characters.