Mercurial > vim
view runtime/keymap/README.txt @ 33780:377ed6ab612c v9.0.2110
patch 9.0.2110: [security]: overflow in ex address parsing
Commit: https://github.com/vim/vim/commit/060623e4a3bc72b011e7cd92bedb3bfb64e06200
Author: Christian Brabandt <cb@256bit.org>
Date: Tue Nov 14 21:33:29 2023 +0100
patch 9.0.2110: [security]: overflow in ex address parsing
Problem: [security]: overflow in ex address parsing
Solution: Verify that lnum is positive, before substracting from
LONG_MAX
[security]: overflow in ex address parsing
When parsing relative ex addresses one may unintentionally cause an
overflow (because LONG_MAX - lnum will overflow for negative addresses).
So verify that lnum is actually positive before doing the overflow
check.
Signed-off-by: Christian Brabandt <cb@256bit.org>
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Thu, 16 Nov 2023 22:15:12 +0100 |
parents | 3fc0f57ecb91 |
children |
line wrap: on
line source
keymap files for Vim One of these files is loaded when the 'keymap' option is set. The name of the file consists of these parts: {language}[-{layout}][_{encoding}].vim {language} Name of the language (e.g., "hebrew", "greek") {layout} Optional: name of the keyboard layout (e.g., "spanish", "russian3"). When omitted the layout of the standard US-english keyboard is assumed. {encoding} Optional: character encoding for which this keymap works. When omitted the "normal" encoding for the language is assumed. Use the value the 'encoding' option: lower case only, use '-' instead of '_'. Each file starts with a header, naming the maintainer and the date when it was last changed. If you find a problem in a keymap file, check if you have the most recent version. If necessary, report a problem to the maintainer. The format of the keymap lines below "loadkeymap" is explained in the Vim help files, see ":help keymap-file-format".