Basically, the delay is linked to the increased security and it depends the chosen hash function.
As explained in the links above, we will implement in the next version a new option to enable the caller to choose which PRF function to choose : this will speed things for SHA512 and Whirlpool.
TrueCrypt use of really small iterations count made it very quick to mount volume, which is not good from the security point of view. Compared to that, VeraCrypt will always be slower but this affects only mounting and not read/write operations.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
thanks for keeping Truecrypt spirit alive, after the project was abandoned.
My product has a script like this:-
veracrypt.exe volume /l x: /q
This script worked great with Truecrypt 7.1a
it strips the UI down to just the password and mounts X: with the file 'volume'
now theres a very long wait (~1 minute?)
both my original volume (volume.tc) and the new one are 8Gb with the plausible deniabilty thing for a 2nd password.
How can I avoid the long wait?
thanks
Yosef
Hi,
We have answered similar questions in the past and here are two links that discuss this :
https://sourceforge.net/p/veracrypt/discussion/technical/thread/77d58591/#5764
https://veracrypt.codeplex.com/discussions/549728
Basically, the delay is linked to the increased security and it depends the chosen hash function.
As explained in the links above, we will implement in the next version a new option to enable the caller to choose which PRF function to choose : this will speed things for SHA512 and Whirlpool.
TrueCrypt use of really small iterations count made it very quick to mount volume, which is not good from the security point of view. Compared to that, VeraCrypt will always be slower but this affects only mounting and not read/write operations.