01-06-2018, 10:50 AM
again, you do not need to guess.
The only way to be 100% sure if the hash is formatted/converted correctly is to use the exact same version of the software you used some years ago (the old wallet software, not a newer version of it) and generate a key with it.
After that you encrypt that wallet and you will see that the same problem happens with hashcat, i.e. that the public key/address is using the uncompressed format while hashcat expects the new one. Therefore you convert this test hash to the compressed version (you can also use ku for this) and try to crack this test "hash" that was generated with the same software version as your original "hash"/wallet.
If it successfully cracks after converting it to the compressed format, the hash that you are targetting to crack (not the test hash) will also be crackable for sure (assuming that you test the correct password candidates).
The only way to be 100% sure if the hash is formatted/converted correctly is to use the exact same version of the software you used some years ago (the old wallet software, not a newer version of it) and generate a key with it.
After that you encrypt that wallet and you will see that the same problem happens with hashcat, i.e. that the public key/address is using the uncompressed format while hashcat expects the new one. Therefore you convert this test hash to the compressed version (you can also use ku for this) and try to crack this test "hash" that was generated with the same software version as your original "hash"/wallet.
If it successfully cracks after converting it to the compressed format, the hash that you are targetting to crack (not the test hash) will also be crackable for sure (assuming that you test the correct password candidates).