02-04-2022, 01:23 PM
(This post was last modified: 02-04-2022, 02:06 PM by 4Str4yC4t.
Edit Reason: I felt it necessary and I'm human? More data was added for the discussion.
)
(01-30-2022, 08:03 PM)Snoopy Wrote: you will need the first 512 bytes of the container see
https://hashcat.net/wiki/doku.php?id=fre...pt_volumes
and no, this type of hashcat will do everything for you will not happen (except the basic hash guessing)
the user has to know what he is doing, what he is attacking and he is in charge to prepare the target, hashlists, wordlists, masks, rules and so on (there are penty examples already shipped)
EDIT:
True/Veracrypt attack input is binary data, so you will "see" no hash for this, also, you have to provide a outputfile otherwise your found password is only shown on command line and maybe you missed it
Thank You very much for your response. So, what's happening when I supply the name of an actual True/VeraCrypt container file is that hashcat is literally thinking the filename is the hash. If this is the case, it's no wonder I'm not having any success.
I have since created a distinct hashfile using a disk editor to pull the first 512 bytes into a file.
If the software will not hold my hands then it maybe it could use tough love on me and at least respond with a message that tells me what I am attempting to do is going to produce no good results. A simple filesize check could throw up a warning at least. "The has you have provided is not 512 bytes in size. Are you sure you are providing a hash?" Or whatever size is appropriate for the encryption at hand.
As a programmer myself, I know it would be very easy to check and see if the "hash" supplied by the end user ends in an extension of .tc (or .vc for veracrypt?) as well. This could be another "red flag".
Lastly, I've read a post somewhere that says if you always select one of the 1536 bit methods of TrueCrypt/VeraCrypt this will allow you to skip the others if you don't know exactly how you encrypted it to begin with.
There are literally like 36 different options for TrueCrypt/VeraCrypt and 12 of those are the 1536-bit methods. I have no idea what encryption I used. Is my safest but assured bet to try the 12 1536-bit "-m" options to crack my TrueCrypt/VeraCrypt passwords?
HashCat Help Screen with highlights by me.
I read somewhere in another post that the 1536-bit methods will default to taking care of the lesser bit options but I don't think it works the other way around.
No, I'm not missing my password. I'm looking at the 0/1 digest stat in the application. 0/1 I'm assuming means no luck for me.