Improve UNC security setting usability by allowing wildcards

[wpcoc]

1.78.1 recently introduced UNC path filtering (see commit 6a995c4). In doing so, this created a barrier to opening simple text files on local network servers, which is a major frustration. I would prefer an option to just switch this feature off (but I probably don't understand how serious the issue is when UNC paths are misused). In the meantime, I have attempted to use wildcards to capture the servers on the network, which use a naming convention. But the UNC path filters do not allow wildcards, meaning UNC paths on the same network need to be added manually in each case.

I propose allowing wildcards on this setting, such that .example.com would cover \server1.example.com, \server2.example.com, etc. Also, the following would work: server, which would match server1, server2, etc.

This may render the security aspect of this setting less useful - there's often a trade-off between usability and security.

[bpasero]

/duplicate #182055

[vscodenpa]

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.

Happy Coding!