[vim/vim] syntax highlighter: gpg.conf: Drop dangerous use-embedded-filename (PR #13961)

28 views
Skip to first unread message

dkg

unread,
Feb 2, 2024, 5:03:09 PMFeb 2
to vim/vim, Subscribed

The syntax highlighter is likely to encourage people to use the listed commands.

but use-embedded-filename is a dangerous option that can cause GnuPG to write arbitrary data to arbitrary files whenever GnuPG encounters malicious data.

GnuPG upstream explicitly warns against using this option:

https://dev.gnupg.org/T4500

I recommend that vim not encourage users to place this option in their gpg.conf by highlighting it as a valid option.

I've also asked GnuPG upstream to explicitly deprecate the option due to its hazardous nature:

https://dev.gnupg.org/T6972


You can view, comment on, or merge this pull request online at:

  https://github.com/vim/vim/pull/13961

Commit Summary

  • d7f5fb4 syntax highlighter: gpg.conf: Drop dangerous use-embedded-filename

File Changes

(1 file)

Patch Links:


Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/13961@github.com>

dkearns

unread,
Feb 2, 2024, 10:06:44 PMFeb 2
to vim/vim, Subscribed

Would it be better to highlight it as an error?


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/13961/c1925034986@github.com>

Christian Brabandt

unread,
Feb 3, 2024, 4:04:15 AMFeb 3
to vim/vim, Subscribed

But error is clearly wrong, as it is still supported. Not sure if we use Warning highlighting in syntax scripts.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/13961/c1925229467@github.com>

dkearns

unread,
Feb 3, 2024, 6:57:03 AMFeb 3
to vim/vim, Subscribed

For better or worse, Error is the commonly used group for deprecated features but there's some use of WarningMsg in more recent additions. javascript.vim uses Exception, which seems like quite the stretch.

@dpkg, this syntax file needs a maintainer if you're willing and able.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/13961/c1925301444@github.com>

Ajit-Thakkar

unread,
Feb 3, 2024, 7:12:32 AMFeb 3
to vim/vim, Subscribed

Fortran.vim uses Todo highlighting for obsolescent features.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/13961/c1925304957@github.com>

Christian Brabandt

unread,
Feb 11, 2024, 12:21:33 PMFeb 11
to vim/vim, Subscribed

Closed #13961 via 6d91227.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/13961/issue_event/11767663951@github.com>

Christian Brabandt

unread,
Feb 11, 2024, 12:21:57 PMFeb 11
to vim/vim, Subscribed

I marked it with WarningMsg for now, since it looks like this option isn't going away from gpg according to the referenced tickets.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/13961/c1937814684@github.com>

dkg

unread,
Feb 22, 2024, 3:52:33 PMFeb 22
to vim/vim, Subscribed

@dkg, this syntax file needs a maintainer if you're willing and able.

I'm not a vim user, let alone comfortable enough with vim to be a maintainer, but thanks for the offer. I'm just trying to clean up dangerous corners of the ecosystem.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/13961/c1960293370@github.com>

dkearns

unread,
Feb 23, 2024, 12:06:30 PMFeb 23
to vim/vim, Subscribed

I see, well thank you for your thankless efforts.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/13961/c1961688680@github.com>

Reply all
Reply to author
Forward
0 new messages