diff --git a/doc/chm/VeraCrypt User Guide.chm b/doc/chm/VeraCrypt User Guide.chm index 8d2384aa..8cbd6905 100644 Binary files a/doc/chm/VeraCrypt User Guide.chm and b/doc/chm/VeraCrypt User Guide.chm differ diff --git a/doc/html/Header Key Derivation.html b/doc/html/Header Key Derivation.html index d8896904..f922d676 100644 --- a/doc/html/Header Key Derivation.html +++ b/doc/html/Header Key Derivation.html @@ -65,14 +65,16 @@ PIM field (Per PIM value is not specified or if it is equal to zero, VeraCrypt uses the default values expressed below:

When a PIM value is given by the user, the number of iterations of the key derivation function is calculated as follows:

diff --git a/doc/html/Personal Iterations Multiplier (PIM).html b/doc/html/Personal Iterations Multiplier (PIM).html index 5271ced2..02921072 100644 --- a/doc/html/Personal Iterations Multiplier (PIM).html +++ b/doc/html/Personal Iterations Multiplier (PIM).html @@ -44,7 +44,9 @@ Header Key Derivation).

When a PIM value is specified, the number of iterations is calculated as follows:

Prior to version 1.12, the security of a VeraCrypt volume was only based on the password strength because VeraCrypt was using a fixed number of iterations.
With the introduction of PIM, VeraCrypt has a 2-dimensional security space for volumes based on the couple (Password, PIM). This provides more flexibility for adjusting the desired security level while also controlling the performance of the mount/boot operation.