Mercurial > vim
diff runtime/doc/usr_23.txt @ 14999:2b30a2b4bde2
Update runtime files
commit https://github.com/vim/vim/commit/ba3ff539303c7bb6e46a6802dce3c7b2e55284e0
Author: Bram Moolenaar <Bram@vim.org>
Date: Sun Nov 4 14:45:49 2018 +0100
Update runtime files
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Sun, 04 Nov 2018 15:00:08 +0100 |
parents | 5c5908e81e93 |
children | af69c9335223 |
line wrap: on
line diff
--- a/runtime/doc/usr_23.txt +++ b/runtime/doc/usr_23.txt @@ -208,15 +208,17 @@ encryption key, just like the "-x" argum LIMITS ON ENCRYPTION -The encryption algorithm used by Vim is weak. It is good enough to keep out -the casual prowler, but not good enough to keep out a cryptology expert with -lots of time on his hands. Also you should be aware that the swap file is not -encrypted; so while you are editing, people with superuser privileges can read -the unencrypted text from this file. - One way to avoid letting people read your swap file is to avoid using one. -If the -n argument is supplied on the command line, no swap file is used -(instead, Vim puts everything in memory). For example, to edit the encrypted -file "file.txt" without a swap file use the following command: > +The encryption algorithm used by Vim is not very strong. It is good enough to +keep out the casual prowler, but not good enough to keep out a cryptology +expert with lots of time on his hands. The text in the swap file and the undo +file is also encrypted. However, this is done block-by-block and may reduce +the time needed to crack a password. You can disable the swap file, but then +a crash will cause you to lose your work, since Vim keeps all the text in +memory only. The undo file can be disabled with the only disadvantage that +you can't undo after unloading the buffer. + To avoid using a swap file, supply the -n argument on the command line. +For example, to edit the encrypted file "file.txt" without a swap file use the +following command: > vim -x -n file.txt