To be honest I'm not sure of what I did about the extracted data. So maybe / probably the problem comes from here. I wouldn't be surprised.
If I could get further informations about how I can create precisely this binary file that would be for sure welcomed
For my password, its length is of about 40 characters. I know that I'd decrypted it successfully one time at least (with the Veracrypt program). But when I retried an other day, I had forgotten the password. So it's possible to hash the password and it's not too long.
It if was, I would have never been able to decrypt it, right ?
And for the rejected password, I used to get 0.00% on each try.
I've done what you tole me and I've created a volume with random data and the password 0123456789*. I've put it in a .dict and ran the attack -a 0 with the .dict against the volume.
And with the -m 13723 the status was "cracked" and got the "Candidates #1 : hashcat -> 0123456789*".
So that worked I guess.
PS: I don't know if I mentioned it, but for the "real volume" I used to get the "Exhausted" status at the end of the process.
Plus when I was trying to crack it, the "Candidates #1" line had a hex value starting with "$HEX[ hex value ] -> $HEX[ hex value ]". I don't know if Iit's possible to extract informations from this hex values ?
If I could get further informations about how I can create precisely this binary file that would be for sure welcomed
For my password, its length is of about 40 characters. I know that I'd decrypted it successfully one time at least (with the Veracrypt program). But when I retried an other day, I had forgotten the password. So it's possible to hash the password and it's not too long.
It if was, I would have never been able to decrypt it, right ?
And for the rejected password, I used to get 0.00% on each try.
I've done what you tole me and I've created a volume with random data and the password 0123456789*. I've put it in a .dict and ran the attack -a 0 with the .dict against the volume.
And with the -m 13723 the status was "cracked" and got the "Candidates #1 : hashcat -> 0123456789*".
So that worked I guess.
PS: I don't know if I mentioned it, but for the "real volume" I used to get the "Exhausted" status at the end of the process.
Plus when I was trying to crack it, the "Candidates #1" line had a hex value starting with "$HEX[ hex value ] -> $HEX[ hex value ]". I don't know if Iit's possible to extract informations from this hex values ?