On 8/31/22 9:21 AM, Richard Purdie wrote:
On Wed, 2022-08-31 at 18:17 +0200, Alexander Kanavin wrote:
I have to wonder, what is really going on there? :-) This never ending
stream of CVEs makes vim formally the most insecure item in core. Does
anyone know?
Personally I suspect some kind of
On Wed, 31 Aug 2022 at 18:21, Richard Purdie
wrote:
> > I have to wonder, what is really going on there? :-) This never ending
> > stream of CVEs makes vim formally the most insecure item in core. Does
> > anyone know?
>
> Personally I suspect some kind of bug bounty system may be influencing
>
"Alexander Kanavin" writes:
> I have to wonder, what is really going on there? :-) This never ending
> stream of CVEs makes vim formally the most insecure item in core. Does
> anyone know?
Is it rhetorical question? :)
Vim has very old codebase and nobody carried about security at that
time.
On Wed, 2022-08-31 at 18:17 +0200, Alexander Kanavin wrote:
> I have to wonder, what is really going on there? :-) This never ending
> stream of CVEs makes vim formally the most insecure item in core. Does
> anyone know?
Personally I suspect some kind of bug bounty system may be influencing
I have to wonder, what is really going on there? :-) This never ending
stream of CVEs makes vim formally the most insecure item in core. Does
anyone know?
Alex
On Wed, 31 Aug 2022 at 18:07, Richard Purdie
wrote:
>
> Addresses CVE-2022-2980, CVE-2022-2946 and CVE-2022-2982.
>
> Signed-off-by:
Addresses CVE-2022-2980, CVE-2022-2946 and CVE-2022-2982.
Signed-off-by: Richard Purdie
---
meta/recipes-support/vim/vim.inc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-support/vim/vim.inc b/meta/recipes-support/vim/vim.inc
index 5b95ab2625c..33a82992433
