you might need to have a look at the Aes Crypt file format page:
https://www.aescrypt.com/aes_file_format.html
They explain how the file format is and how it changed over time
there is "AES" at the start of the file (first 3 bytes, "A", "E" and "S") and after that comes a version number.
I think aescrypt2hashcat.pl only supports the latest version, because it was the only one we had some example
hash:pass
pairs. This doesn't mean that the code couldn't work for sure, but somebody would need to investigate what the differences are to extract the data from the *.aes file and also if the code to verify if the password candidates are correct changed over time or didn't change at all over time.
I would say you will need to start with the file format version number (the byte after the "AES" at the start.
You would probably need some hex editor to open (a copy/backup of) the file and view the single bytes and compare them to that "AES - File Format" page linked above (https://www.aescrypt.com/aes_file_format.html), like HxD for windows etc
https://www.aescrypt.com/aes_file_format.html
They explain how the file format is and how it changed over time
there is "AES" at the start of the file (first 3 bytes, "A", "E" and "S") and after that comes a version number.
I think aescrypt2hashcat.pl only supports the latest version, because it was the only one we had some example
hash:pass
pairs. This doesn't mean that the code couldn't work for sure, but somebody would need to investigate what the differences are to extract the data from the *.aes file and also if the code to verify if the password candidates are correct changed over time or didn't change at all over time.
I would say you will need to start with the file format version number (the byte after the "AES" at the start.
You would probably need some hex editor to open (a copy/backup of) the file and view the single bytes and compare them to that "AES - File Format" page linked above (https://www.aescrypt.com/aes_file_format.html), like HxD for windows etc