okay, I will probably start to implement this, starting with the AES-128 variant.
Not sure how long it will take and if it will be merged into hashcat (and available in beta) soon.
But I will take the challenge and try to implement it... from a technical perspective the "most difficult" part is the 2 heavy loops which are kind of uncommon for other hashing algorithms (but we already have some examples of them)... We would need two heavily iterated loops (both for PBKDF2-HMAC-SHA512 and the AES unwrapping loop).
The good thing is that axcrypt2john will still be able to extract the data of both of them so we do not need to wait for an update there... but it's still important that the users selects the correct hash type in hashcat (when it will be available) otherwise it will be uncrackable of course (well, the user could find out that this algo is wrong and move on to the other variant).
Thx
update: I proposed this change for the hashcat source code (both new AxCrypt 2 algos): https://github.com/hashcat/hashcat/pull/2517
We could/would need to wait until reviewed/accepted/merged and new beta is available... in theory you could always test it also by building it from the source code yourself in the meantime. thx
Not sure how long it will take and if it will be merged into hashcat (and available in beta) soon.
But I will take the challenge and try to implement it... from a technical perspective the "most difficult" part is the 2 heavy loops which are kind of uncommon for other hashing algorithms (but we already have some examples of them)... We would need two heavily iterated loops (both for PBKDF2-HMAC-SHA512 and the AES unwrapping loop).
The good thing is that axcrypt2john will still be able to extract the data of both of them so we do not need to wait for an update there... but it's still important that the users selects the correct hash type in hashcat (when it will be available) otherwise it will be uncrackable of course (well, the user could find out that this algo is wrong and move on to the other variant).
Thx
update: I proposed this change for the hashcat source code (both new AxCrypt 2 algos): https://github.com/hashcat/hashcat/pull/2517
We could/would need to wait until reviewed/accepted/merged and new beta is available... in theory you could always test it also by building it from the source code yourself in the meantime. thx