Hi All,
I have just finished encrypting my first VeraCrypt drive.
It is 1Tb capacity, and is configured to have a Hidden Volume.
When I came to mount this drive, it took approximately 6.75 minutes before I could access it.
A similar drive, but encrypted in TrueCrypt, takes only a few seconds to be mounted.
(a) Is this length of time normal? -- (b) Is there any way of speeding up the process or (c) should I just revert to TrueCrypt?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The extra mount time is due to the encreased iterations in VeraCrypt and it can have a visible effect on slow CPU.
A new feature was introduced in VeraCrypt 1.13 to speed up mounting for users how have strong password. In your case, just use a password of a at least 20 characters and set the PIM to a small value (do this through the change password functionality). Minimal value is 1 which still give an encryption stronger 16x compared to TrueCrypt.
Hi Mounir IDRASSI. Many thanks for that info.
I just wish I had known about this before creating the new volume.
I'm sure there are those out there who are quite willing to go through such a time consuming delay and/or procedure, but I doubt my data is of such great interest to otthers to warrant it.
I shall revert to TrueCrypt which has, after all, served me well for such a long time.
Thanks again,
Ian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@Mounir Oh no, this is such nonsense. I have one of the most powerful laptops money can buy, running W10 64-bit and this wait-very-long mount time is totally unacceptable.
On my previous very powerful machine W7 had to be restarted whenever I wanted to start dictating (DNS) with a particularly clunky app but which I have to use for professional purposes.
So back in the real world you do not have to start up your M$ OS "once a day"... what about when you want to change from one user to the next?
Do I want/need encryption that the NSA would have difficulty breaking? ... not at all. So GIVE-ME-THE-CHOICE.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Mounir, I hope you will consider removing the restrictions for using PIM and letting users choose the number of iterations regardless of password length.
I imagine you're doing this to protect those who might not know better and whose lives may depend on keeping a volume secure.
Unfortunately, you can't protect people from themselves. Punishing the use of shorter passwords through longer mount times will drive people to use long passwords to use PIM and circumvent the iteration count. However, this runs into the same problems as enforcing password complexity. People will be annoyed and grudgingly use it, set iterations to 1, and use passwords like 12345678901234567890 or string together the names of their cats and children.
The time penalty for mistyping a password is the main reason I can't bring myself to recommend VeraCrypt to family and friends. Or if I do, I'd tell them to create a volume with TrueCrypt first, uninstall TrueCrypt, and then use VeraCrypt to access their volumes so they don't have to deal with the long mount/error times.
You are going to continue encounting resistance and anger with this because creating an encrypted volume can be a large time commitment and it isn't clear from before, what performance you can expect after the process is done.
Give the program strong defaults and teach people the value of using a higher iteration count but please make it possible to reduce the iterations for users who don't want or need it.
Last edit: Positronic Tomato 2016-01-05
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
we already have an exhaustive thread on that topic here: long boot time
See my post, which basically reflects your notion, and the 9 pages before.
You previous poster Mike Rodent has already contributed to that as well :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi All,
I have just finished encrypting my first VeraCrypt drive.
It is 1Tb capacity, and is configured to have a Hidden Volume.
When I came to mount this drive, it took approximately 6.75 minutes before I could access it.
A similar drive, but encrypted in TrueCrypt, takes only a few seconds to be mounted.
(a) Is this length of time normal? -- (b) Is there any way of speeding up the process or (c) should I just revert to TrueCrypt?
Hi,
The extra mount time is due to the encreased iterations in VeraCrypt and it can have a visible effect on slow CPU.
A new feature was introduced in VeraCrypt 1.13 to speed up mounting for users how have strong password. In your case, just use a password of a at least 20 characters and set the PIM to a small value (do this through the change password functionality). Minimal value is 1 which still give an encryption stronger 16x compared to TrueCrypt.
You can read more about PIM in the documentation: https://veracrypt.codeplex.com/wikipage?title=Personal%20Iterations%20Multiplier%20%28PIM%29
Hi Mounir IDRASSI. Many thanks for that info.
I just wish I had known about this before creating the new volume.
I'm sure there are those out there who are quite willing to go through such a time consuming delay and/or procedure, but I doubt my data is of such great interest to otthers to warrant it.
I shall revert to TrueCrypt which has, after all, served me well for such a long time.
Thanks again,
Ian
@Mounir Oh no, this is such nonsense. I have one of the most powerful laptops money can buy, running W10 64-bit and this wait-very-long mount time is totally unacceptable.
On my previous very powerful machine W7 had to be restarted whenever I wanted to start dictating (DNS) with a particularly clunky app but which I have to use for professional purposes.
So back in the real world you do not have to start up your M$ OS "once a day"... what about when you want to change from one user to the next?
Do I want/need encryption that the NSA would have difficulty breaking? ... not at all. So GIVE-ME-THE-CHOICE.
Mounir, I hope you will consider removing the restrictions for using PIM and letting users choose the number of iterations regardless of password length.
I imagine you're doing this to protect those who might not know better and whose lives may depend on keeping a volume secure.
Unfortunately, you can't protect people from themselves. Punishing the use of shorter passwords through longer mount times will drive people to use long passwords to use PIM and circumvent the iteration count. However, this runs into the same problems as enforcing password complexity. People will be annoyed and grudgingly use it, set iterations to 1, and use passwords like 12345678901234567890 or string together the names of their cats and children.
The time penalty for mistyping a password is the main reason I can't bring myself to recommend VeraCrypt to family and friends. Or if I do, I'd tell them to create a volume with TrueCrypt first, uninstall TrueCrypt, and then use VeraCrypt to access their volumes so they don't have to deal with the long mount/error times.
You are going to continue encounting resistance and anger with this because creating an encrypted volume can be a large time commitment and it isn't clear from before, what performance you can expect after the process is done.
Give the program strong defaults and teach people the value of using a higher iteration count but please make it possible to reduce the iterations for users who don't want or need it.
Last edit: Positronic Tomato 2016-01-05
Dear Positronic Tomato,
we already have an exhaustive thread on that topic here:
long boot time
See my post, which basically reflects your notion, and the 9 pages before.
You previous poster Mike Rodent has already contributed to that as well :)