Update Powershell C&P: Use name instead of number to clarify Security Option #441
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.
What and Why
This change allows for easier auditing by those not familiar with Powershell.
It replaces the
-bor 3072
flag with[System.Net.SecurityProtocolType]::Tls12
which are equivalent. However, the TLS12 is both easier to read and for powershell newbies/non-programmers it's easier to find the documentation.Info:
SecurityProtocolType name-to-number mapping. ie
3072
is equivalent toTls12
Docs on SecurityPointManager