This project has moved and is read-only. For the latest updates, please go here.

File Mounting Seems To Take Longer Than TC

Topics: Technical Issues
Nov 26, 2014 at 4:31 AM
Edited Nov 26, 2014 at 4:41 AM
When I mount the same sized file (8GB) in Veracrypt it seems to take much longer than in Truecrypt.
Is this normal?
The VC file uses Whirlpool, TC uses Ripemd-160.
Both use the same encryption algorithm.
This is under Windows 7 pro 32bit.
Nov 26, 2014 at 7:49 AM
First, the fact that mounting takes longer is known and explained in the project description of VeraCrypt. It is due to the increased iterations count and "This enhanced security adds some delay only to the opening of encrypted partitions without any performance impact to the application use phase. This is acceptable to the legitimate owner but it makes it much more harder for an attacker to gain access to the encrypted data."

Moreover, this question has been asked many times and I already gave detailed explanation about it. See for example
As in TrueCrypt, VeraCrypt tries all algorithms sequentially. In version 1.0e, Ripemd-160 is the first on the list and Whirlpool is the last. So, if you use 1.0e, you'll get the longest mounting time when using Whirlpool. In version 1.0f-BETA, SHA512 is the first, followed by Whirlpool and Ripemd-160 is the last. Thus, in this version, the mounting time using Whirlpool will be quicker.

In the final 1.0f, we'll introduce an algorithm selection in the password dialog so that the legitimate user can choose the correct derivation algorithm so that VeraCrypt will not lose time trying non application algorithms.
Nov 26, 2014 at 8:15 AM
Edited Nov 27, 2014 at 12:35 AM
Thank you very much for your professional response and thank you very much for the work and effort that you are putting into the project.

It's definitely worth a donation. (Done - €28)

Best of luck with it.