VeraCrypt
aboutsummaryrefslogtreecommitdiff
path: root/doc/html/VeraCrypt RAM Encryption.html
diff options
context:
space:
mode:
authorHelmut K. C. Tessarek <tessarek@evermeet.cx>2025-01-31 23:18:26 +0100
committerGitHub <noreply@github.com>2025-01-31 23:18:26 +0100
commit498dff9013d18e5978ab77c14ea2b2d0229603a4 (patch)
tree7f172f9c2945691ac9b1fb08f963a2263fd6942f /doc/html/VeraCrypt RAM Encryption.html
parentc71fa14dc09fd7f31282f6ce4fdf3db547b9b827 (diff)
downloadVeraCrypt-498dff9013d18e5978ab77c14ea2b2d0229603a4.tar.gz
VeraCrypt-498dff9013d18e5978ab77c14ea2b2d0229603a4.zip
refactor: use the term unmount instead of dismount (#1478)HEADmaster
* refactor: use UNMOUNT instead of DISMOUNT in code This change updates the term DISMOUNT in constants to UNMOUNT. Other occurrences (e.g. variable names) are left alone for now. * refactor(ui): use unmount instead of dismount This change updates the GUI text and replaces dismount with unmount. * docs: update term dismount -> unmount * refactor(cmdline): add unmount This change adds an argument 'unmount' for command line usage, while trying to deprecate the old disnount argument. The current dismount argument/flag will still work to not introduce a breaking change. * docs: mention that /dismount is deprecated This change fixes the shorthand version of the argument /unmount It also adds back the info for /dismount and that it is deprecated.
Diffstat (limited to 'doc/html/VeraCrypt RAM Encryption.html')
-rw-r--r--doc/html/VeraCrypt RAM Encryption.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/html/VeraCrypt RAM Encryption.html b/doc/html/VeraCrypt RAM Encryption.html
index 5bfb6aa5..033a4522 100644
--- a/doc/html/VeraCrypt RAM Encryption.html
+++ b/doc/html/VeraCrypt RAM Encryption.html
@@ -58,7 +58,7 @@
<li>The master keys are decrypted for every request, requiring a fast decryption algorithm. For this, ChaCha12 is utilized.</li>
<li>Once a volume is mounted, its master keys are immediately encrypted using the described algorithm.</li>
<li>For each I/O request for a volume, the master keys are decrypted only for the duration of that request and then securely wiped.</li>
- <li>Upon volume dismounting, the encrypted master keys are securely removed from memory.</li>
+ <li>Upon volume unmounting, the encrypted master keys are securely removed from memory.</li>
<li>At Windows shutdown or reboot, the memory region allocated during startup is securely wiped.</li>
</ol>