diff options
author | Yee Cheng Chin <ychin.git@gmail.com> | 2023-10-01 09:13:22 +0200 |
---|---|---|
committer | Christian Brabandt <cb@256bit.org> | 2023-10-01 09:19:18 +0200 |
commit | 6ee7b521fa7531ef356ececc8be7575c3800f872 (patch) | |
tree | 0837915c4a965902d369e8f2a0b0748b94f9dc41 /runtime/doc/options.txt | |
parent | 7ece036d72cf639b05d3936183220bec7179bf63 (diff) |
patch 9.0.1968: cmdline completion should consider key optionv9.0.1968
Problem: cmdline completion should consider key option
Solution: Disable cmdline completion for key option, slightly
refactor how P_NO_CMD_EXPAND is handled
Harden crypto 'key' option: turn off cmdline completion, disable set-=
"set-=" can be used maliciously with a crypto key, as it allows an
attacker (who either has access to the computer or a plugin author) to
guess a substring by observing the modified state. Simply turn off
set+=/-=/^= for this option as there is no good reason for them to be
used.
Update docs to make that clear as well.
Also, don't allow cmdline completion for 'key' as it just shows *****
which is not useful and confusing to the user what it means (if the user
accidentally hits enter they will have replaced their key with "*****"
instead).
Move logic to better location, don't use above 32-bit for flags
Move P_NO_CMD_EXPAND to use the unused 0x20 instead of going above
32-bits, as currently the flags parameter is only 32-bits on some
systems. Left a comment to warn that future additions will need to
change how the flags work either by making it 64-bit or split into two
member vars.
Also, move the logic for detecting P_NO_CMD_EXPAND earlier so it's not
up to each handler to decide, and you won't see the temporary "..." that
Vim shows while waiting for completion handler to complete.
closes: #13224
Signed-off-by: Christian Brabandt <cb@256bit.org>
Co-authored-by: Yee Cheng Chin <ychin.git@gmail.com>
Diffstat (limited to 'runtime/doc/options.txt')
-rw-r--r-- | runtime/doc/options.txt | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/runtime/doc/options.txt b/runtime/doc/options.txt index 090399af03..a24dd0490d 100644 --- a/runtime/doc/options.txt +++ b/runtime/doc/options.txt @@ -4928,6 +4928,8 @@ A jump table for the options with a short description can be found at |Q_op|. "echo &key". This is to avoid showing it to someone who shouldn't know. It also means you cannot see it yourself once you have set it, be careful not to make a typing error! + You also cannot use |:set-=|, |:set+=|, |:set^=| on this option to + prevent an attacker from guessing substrings in your key. You can use "&key" in an expression to detect whether encryption is enabled. When 'key' is set it returns "*****" (five stars). |