07-08-2020, 09:18 PM
I was able to follow your good instructions above up until the part where I tried to understand "run the conversion script (from the .aes file to a "hash" that hashcat supports) with the command above." Would you explain what is meant by "to a 'hash' that hashcat supports". I did run the command perl aescrypt2hashcat.pl file.aes as instructed inside the tools folder with my aes file copied inside the tools folder. Is there any editing involved with the aescrypt2hashcat.pl script before running it with the command given above (perl aescrypt2hashcat.pl file.aes)?
My aes file is encrypted by AES Crypt back in March, 2016 and nothing has changed since then in terms of it was stored on a thumb drive up until recently when I copied it to a folder on my laptop hard drive. Of course the password has been forgotten, hence the need to crack. However, something is not as it should be with my aes file. I have continuously received the same ERROR message from the script aescrypt2hashcat.pl which is...
"ERROR: The file doesn't seem to be a correct aescrypt file (signature mismatch)". Any ideas how to overcome this?
I don't know how to solve this if the aescrypt2hashcat.pl script doesn't recognize it as a genuine aes file. I am certain however the original aes file was indeed created by AES Crypt in 2016 and no other cryptography software. By the way, at the beginning of 2016 AES Crypt came out with version 2 (AES 256) as opposed to version 1 (AES 128) and the aescrypt2hashcat.pl script works for version 2. In conclusion, I'm not sure what to do at this point.
My aes file is encrypted by AES Crypt back in March, 2016 and nothing has changed since then in terms of it was stored on a thumb drive up until recently when I copied it to a folder on my laptop hard drive. Of course the password has been forgotten, hence the need to crack. However, something is not as it should be with my aes file. I have continuously received the same ERROR message from the script aescrypt2hashcat.pl which is...
"ERROR: The file doesn't seem to be a correct aescrypt file (signature mismatch)". Any ideas how to overcome this?
I don't know how to solve this if the aescrypt2hashcat.pl script doesn't recognize it as a genuine aes file. I am certain however the original aes file was indeed created by AES Crypt in 2016 and no other cryptography software. By the way, at the beginning of 2016 AES Crypt came out with version 2 (AES 256) as opposed to version 1 (AES 128) and the aescrypt2hashcat.pl script works for version 2. In conclusion, I'm not sure what to do at this point.