Support getting cert check options from PowerShell SessionOption #15
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PowerShell/PowerShell#13577 has more details on the background of this issue but there are 2 issues with cert verification with WSMan endpoints
-SessionOption (New-PSSessionOption -SkipCACheck -SkipCNCheck)
-SessionOption
value from PowerShellsetenv
directly due to .NET's handling of env vars on non-Windows hostsWhat this PR does is
WSManSetSessionOption()
for both the CA and CN skip options inpsrpclient
The first two will allow the
-SkipC*Check
options to pass down and actually work once PowerShell removes the hardcoded check. The last fix gives PowerShell a way to remove that hardcoded check when it knows the client supports certificate verification.Ultimately this will allow an end user of this fork the ability to connect to a WSMan listener and feel secure that the proper verification work is in place but also allow them to disable those checks using the proper PowerShell way like they can do on Windows.