@philsmd, I can recreate this - for both TrueCrypt and Veracrypt, it seems, if a session is specified, but a potfile is not, then ses.potfile is not created on the fly that I can find (on Linux, anyway). Running the same command twice causes another crack (rather than skipping it as already having been cracked). And if I explicitly add "--potfile-path=ses.potfile", it creates a potfile with zero length and nothing is written to it on crack.
Perhaps this is because TrueCrypt and VeraCrypt hashes are read directly from the container/volume? IIRC it used to store the filename in the potfile instead?
Perhaps this is because TrueCrypt and VeraCrypt hashes are read directly from the container/volume? IIRC it used to store the filename in the potfile instead?
~