You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the UseSecurityBestPractices Parameter with $true the underlying Function Set-SChannelProtocol sets a wrong value for the Enabled DWord Property.
Currently the Function sets the value to 0xffffffff, but based on the documentation it should be 1
Quote from TLS 1.1
To disable the TLS 1.1 protocol, create an Enabled entry in the appropriate subkey. This entry does not exist in the registry by default. After you have created the entry, change the DWORD value to 0. To enable the protocol, change the DWORD value to 1.
We had an issue where a Netscaler Client was not able to create a Secure Connection while the enabled value was set to 0xffffffff, but could connect when it had been set to 1
Name Version Path
---- ------- ----
xPSDesiredStateConfiguration 9.1.0 C:\Program Files\WindowsPowerShell\Modules\xPSDesiredStateConfiguration\9.1.0\xPSDesiredStateConfiguration.psd1
The text was updated successfully, but these errors were encountered:
Problem description
When using the
UseSecurityBestPractices
Parameter with $true the underlying FunctionSet-SChannelProtocol
sets a wrong value for theEnabled
DWord Property.Currently the Function sets the value to
0xffffffff
, but based on the documentation it should be1
Quote from TLS 1.1
We had an issue where a Netscaler Client was not able to create a Secure Connection while the
enabled
value was set to0xffffffff
, but could connect when it had been set to1
Verbose logs
DSC configuration
n/a
Suggested solution
Change the Line
$null = New-ItemProperty -Path $registryPath -Name Enabled -Value '0xffffffff' -PropertyType 'DWord' -Force
to
$null = New-ItemProperty -Path $registryPath -Name Enabled -Value '1' -PropertyType 'DWord' -Force
Operating system the target node is running
PowerShell version and build the target node is running
xPSDesiredStateConfiguration version
The text was updated successfully, but these errors were encountered: