diff options
| author | Mounir IDRASSI <mounir.idrassi@idrix.fr> | 2021-12-27 20:13:46 +0100 |
|---|---|---|
| committer | Mounir IDRASSI <mounir.idrassi@idrix.fr> | 2021-12-27 20:14:44 +0100 |
| commit | 7b8ba151b2b6a99521cc6cf6f8c5215b4d36ba62 (patch) | |
| tree | 19be54000d2381641d8a2ea4d6b41bfd55284be1 /doc/html | |
| parent | 7fcd4bce715ea3618b6971a454e88eaad1a72298 (diff) | |
| download | VeraCrypt-7b8ba151b2b6a99521cc6cf6f8c5215b4d36ba62.tar.gz VeraCrypt-7b8ba151b2b6a99521cc6cf6f8c5215b4d36ba62.zip | |
Documentation: clarify that non-cascaded encryption algorithm for system encryption can be inferred from VeraCrypt bootloader only in the case of MBR boot mode.
Diffstat (limited to 'doc/html')
| -rw-r--r-- | doc/html/Encryption Scheme.html | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/html/Encryption Scheme.html b/doc/html/Encryption Scheme.html index 67d669a2..e159c7e8 100644 --- a/doc/html/Encryption Scheme.html +++ b/doc/html/Encryption Scheme.html @@ -81,7 +81,7 @@ Hidden Operating System</a>). If there is a hidden volume within this volume (or <p>* If the size of the active partition is less than 256 MB, then the data is read from the <em>second</em> partition behind the active one (Windows 7 and later, by default, do not boot from the partition on which they are installed).</p> <p>† These parameters are kept secret <em>not</em> in order to increase the complexity of an attack, but primarily to make VeraCrypt volumes unidentifiable (indistinguishable from random data), which would be difficult to achieve if these parameters - were stored unencrypted within the volume header. Also note that if a non-cascaded encryption algorithm is used for system encryption, the algorithm + were stored unencrypted within the volume header. Also note that in the case of legacy MBR boot mode, if a non-cascaded encryption algorithm is used for system encryption, the algorithm <em>is</em> known (it can be determined by analyzing the contents of the unencrypted VeraCrypt Boot Loader stored in the first logical drive track or on the VeraCrypt Rescue Disk).</p> <p>** The master keys were generated during the volume creation and cannot be changed later. Volume password change is accomplished by re-encrypting the volume header using a new header key (derived from a new password).</p> <p> </p> |