The AxCrypt 1 version of hashes that hashcat already supports (-m 13200) is only using AES-128: https://github.com/hashcat/hashcat/blob/...re.cl#L169
I'm not totally sure if AES-256 could be used for AxCrypt 1 too, but I'm pretty sure that hashcat only supports AES-128 for AxCrypt-1 as you can see from the code above.
Maybe you, TomM, can also do some further research and investigate this and create some further new test examples and test other hashes that create $axcrypt$*1* hashes with axcrypt2john.py ? But again, maybe it's off-topic here and the AxCrypt 1 problem should be discuessed in the other thread ? Thx
update: It seems AES-256 is/was not supported with AxCrypt 1 see : https://bitbucket.org/axcryptab/axcrypt-...re/Crypto/
There is no "V1Aes256CryptoFactory.cs" (or in general no Aes256 with V1), only for V2 there are AES256 program files . Of course this assumption is not bullet-proof (there could still be the slight possibility that one version supported it in the past etc... but it's very unlikely... but I would still contact the AxCrypt support if you are really in doubt and maybe mention their answer here etc). Thx
BTW: I think this code and comment (that I accidentally found now while searching for the AxCrypt 1 supported ciphers) does indeed hint that the cipher does not occur in the .axx file metadata, but every "CryptoID" or algorithm is just tested one by one until a hit or each and every one of them failed: https://bitbucket.org/axcryptab/axcrypt-...es-111:112
I'm not totally sure if AES-256 could be used for AxCrypt 1 too, but I'm pretty sure that hashcat only supports AES-128 for AxCrypt-1 as you can see from the code above.
Maybe you, TomM, can also do some further research and investigate this and create some further new test examples and test other hashes that create $axcrypt$*1* hashes with axcrypt2john.py ? But again, maybe it's off-topic here and the AxCrypt 1 problem should be discuessed in the other thread ? Thx
update: It seems AES-256 is/was not supported with AxCrypt 1 see : https://bitbucket.org/axcryptab/axcrypt-...re/Crypto/
There is no "V1Aes256CryptoFactory.cs" (or in general no Aes256 with V1), only for V2 there are AES256 program files . Of course this assumption is not bullet-proof (there could still be the slight possibility that one version supported it in the past etc... but it's very unlikely... but I would still contact the AxCrypt support if you are really in doubt and maybe mention their answer here etc). Thx
BTW: I think this code and comment (that I accidentally found now while searching for the AxCrypt 1 supported ciphers) does indeed hint that the cipher does not occur in the .axx file metadata, but every "CryptoID" or algorithm is just tested one by one until a hit or each and every one of them failed: https://bitbucket.org/axcryptab/axcrypt-...es-111:112