The new "security.allowedUNCHosts" in 1.78.1 setting breaks our workflow. We edit a lot of files on a lot of UNC hosts (around ~3k hosts per user, many users). How can the feature be disabled or all/regex hosts be allowed?
Alternatively, we could try to add all our UNC hosts. The list ist around 5mb (now) and changes on a hourly basis - editing this manually is nonsense, but neither security.allowedUNCHosts nor NODE_UNC_HOST_ALLOWLIST allows for centralized (and realtime) management.
Using a match pattern like \10.2.. or \(.).*.example.com would be our preferred method.
The new "security.allowedUNCHosts" in 1.78.1 setting breaks our workflow. We edit a lot of files on a lot of UNC hosts (around ~3k hosts per user, many users). How can the feature be disabled or all/regex hosts be allowed?
Alternatively, we could try to add all our UNC hosts. The list ist around 5mb (now) and changes on a hourly basis - editing this manually is nonsense, but neither
security.allowedUNCHostsnorNODE_UNC_HOST_ALLOWLISTallows for centralized (and realtime) management.Using a match pattern like \10.2.. or \(.).*.example.com would be our preferred method.