The patch 9.2.0405 effectively disables the use of remote URIs in tag files.
That is, it disables :tag / netrw integration. Is no longer possible to use :tag commands to:
github, gitlab, etc...I believe both scenarios are quite common nowadays and backward compatibility should be provided using a specific option.
In this PR I propose 'tagsecure' because:
https://github.com/vim/vim/pull/20162
(10 files)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.![]()
@MiguelBarro pushed 2 commits.
—
View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
The problem that patch 9.2.0405 attempts to solve is that opening URLs via tags allows environment variable exfiltration. If patch 9.2.0405 was too restrictive then I think the alternative solution (disabling environment expansion in tag URLs) should be used instead.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.![]()
Is this really that common? It's not only about environment variable exfiltration but you know what can happen if your tag lookup starts querying a random URL (which can be quite unexpected)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.![]()