09-04-2014, 02:14 AM
CudaHashcat 1.31 seems to fail under the following circumstances:
Using TrueCrypt 7.1a, create a 1 megabyte encrypted file container as a Standard TrueCrypt volume named Test.tc using the default AES Encryption Algorithm with the RIPEMD-160 Hash Algorithm. Use a simple 4 character password such as Test making it easy to crack. Format the drive, then mount it in TrueCrypt to verify it is readable. Quit TrueCrypt and copy the file container test.tc to a fresh copy of the cudaHashcat-1.30 system.
Using Windows XP SP 3 with an updated NVidia display driver version 337.88 or greater, open a DOS box and change directories to the cudaHashcat-1.30 folder. Create a cmd file Test1.cmd and add the following lines:
cudaHashcat32.exe -a 3 -m 6211 Test.tc ?a?a?a?a
pause
Save, then run the cmd file. On my system(s) Hashcat loads and begins operating as expected, however it processes the entire hash set in about an hour before exiting as if it was unable to find any password.
Adding the known password to a dictionary file and re-running Hashcat with a mode 0 straight attack returns instantly with a status of Exhausted and no password found.
Is there anything I can do to try and track down this type of failure?
Thanks in advance.
Using TrueCrypt 7.1a, create a 1 megabyte encrypted file container as a Standard TrueCrypt volume named Test.tc using the default AES Encryption Algorithm with the RIPEMD-160 Hash Algorithm. Use a simple 4 character password such as Test making it easy to crack. Format the drive, then mount it in TrueCrypt to verify it is readable. Quit TrueCrypt and copy the file container test.tc to a fresh copy of the cudaHashcat-1.30 system.
Using Windows XP SP 3 with an updated NVidia display driver version 337.88 or greater, open a DOS box and change directories to the cudaHashcat-1.30 folder. Create a cmd file Test1.cmd and add the following lines:
cudaHashcat32.exe -a 3 -m 6211 Test.tc ?a?a?a?a
pause
Save, then run the cmd file. On my system(s) Hashcat loads and begins operating as expected, however it processes the entire hash set in about an hour before exiting as if it was unable to find any password.
Adding the known password to a dictionary file and re-running Hashcat with a mode 0 straight attack returns instantly with a status of Exhausted and no password found.
Is there anything I can do to try and track down this type of failure?
Thanks in advance.