-
Notifications
You must be signed in to change notification settings - Fork 8.1k
feat: add TrustedHosts policy config option to allow whitelisting of UNC paths #26688
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
…f UNC paths The default behaviour of assuming any hostname with a `.` in it is not usable in environments where one wishes to refer to a path via FQDN, for example when using DFS to refer to file servers. The configuration option added here allows a group-policy as well as a config-file based approach to whitelisting hosts.
|
@Antvirf please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
PR Summary
Add a configuration option in both registry and config JSON to whitelist server names to be marked as "local intranet zones" as far as script execution is concerned. Otherwise, PS7 cannot execute scripts from remote locations with a
.in the name, breaking e.g. the loading of powershell profiles when the user's Documents directory is redirected to a server referred to via an FQDN.Resolves #12336
PR Context
The default behaviour of assuming any hostname with a
.in it being insecure is not usable in environments where one wishes to refer to a path via FQDN, for example when using DFS to refer to file servers. The configuration option added here allows a group-policy as well as a config-file based approach to whitelisting hosts.PR Checklist
.h,.cpp,.cs,.ps1and.psm1files have the correct copyright headerTBC