In the forum post I also mentioned that it might or might not be possible to detect if the file uses AES-128 or AES-256 from the file metadata alone (it might be the case that you need to enter a password and the software simply tests both until one succeeds or both fail, this is just an assumption but the AxCrypt spec PDF file hints to it that the cipher is not known). Yeah, the only problem is that JTR doesn't support AES-128 for AxCrypt files (which is actually the default one for the free version as far as I can tell). Preferred vector width: char 1, short 1, int 1, long 1 Native vector widths: char 1, short 1, int 1, long 1 Platform #0 name: NVIDIA CUDA, version: OpenCL 1.2 CUDA 10.1.152 Once I realised that, I tried to create multiple accounts with different passwords and I was not able to crack any of them. I can assure that the correct password is in the file /tmp/axcrypt.txt used as a wordlist I double checked and I am able to decrypt it using the normal AxCrypt GUI and works even in a PC with no AxCrypt installed but using AxCryptBruteforcer, so the account is not logged in.Įdit: I am able to crack the test.axx file however that is the only one. I also tried to remove the filename before the hash, nothing changed.
Press 'q' or Ctrl-C to abort, almost any other key for status Loaded 1 password hash (axcrypt2-opencl, AxCrypt 2.x )Ĭost 1 (iteration count) is 63200 for all loaded hashes
0 kommentar(er)
