am I doing something wrong?
#1
hello I extracted a veracrypt hash from a encrypted drive which was encrypted with full drive encryption.
I used dd to achieve that (http://0x31.de/cracking-truecrypt-contai...em-system/)
here I'm using a 13761 mode which is suppose to be the veracrypt one and I tried one with a custom charset which didn't crack it.
I would be thankful if someone gave it a look and told me if this is right.

hashcat32.exe -m 13761 -a 3 --increment --increment-min 7 hash.dd abcdefg?a?a?a?a?a
hashcat32.exe -m 13761 -a 3 -1 ,ro.{5 --increment --increment-min 7 hash.dd abcdefg?1?1?1?1?1
#2
* Does the mask match the password?
* Did you set the correct offset for full drive encryption? Is this one really the same as with TrueCrypt?
* Are you sure the cipher is not cascaded?
#3
The mask should be right, I used " echo "31744/512" | bc " and got out of it "62".
then I used: " dd if=/dev/sdb of=/root/Desktop/512byte-at-offset-31744.dd bs=512 count=1 skip=62 "
so the 31744 offset was applied, but the guy on the site that i provided the link for uses -m 6241 insted of -m 13761 so
maybe thats my issue, should I use 6241 ?
I don't know if it's cascaded, I didn't explicitliy double encrypted it.
I assume the "cascaded cypher" means that the hash was encrypted with something else, which I didn't do.
I just followed the full drive system encryption wizard provided by veracrypt for windows, so if it would be cascaded then it was cascaded by the pretty much left to default settings of the veracrypt wizard.
#4
> but the guy on the site that i provided the link for uses -m 6241 insted of -m 13761 so
This is correct for 6241

> maybe thats my issue, should I use 6241 ?
Maybe, yes. I can't say for sure if the offset should be different for veracrypt. Maybe someone else can?
However, for veracrypt you can not use 6241

> I don't know if it's cascaded, I didn't explicitliy double encrypted it.
So you did created the image or not? How can you be sure then that the mask is correct?
#5
Which image? I extracted the hash with dd exacly like the guy did for the system encrypion.
I'm pretty sure the mask is correct because I remember a good chunk of the password, the mask is the abcdefg?1?1?1?1?1
which consist of the neverchanging letters and 1 which will be replaced with the charset letters, numbers and symbols.
#6
But if hashcat can not find it, it's either an invalid offset or the mask is invalid. To find out which of them is true, I can only see one way. You need to build a bootable veracrypt system and reproduce the steps you described. If you can crack it, you have an invalid mask (or the part you think is known is invalid). If you still can't crack it afterwards it's probably an invalid offset. I can confirm that I've tested hashcats veracrypt implementation successfully with all the images I got so far.