View source for TLS 1.2 Client Support

__FORCETOC__
Wiki for tracking which scripting engines support TLS 1.2 HTTP clients 
and instructions on how to enable support by changing version, running 
command, etc.

==PHP (Coming Soon)==

==ColdFusion (Coming Soon)==



==ASP.Net==

{| class="wikitable"
! style="text-align: center;" | Framework Version
! style="text-align: center;" | TLS 1.2 Support
|-
| style="text-align: center;" | 2.0-3.5
| style="text-align: center; background-color: Red;" | Not Supported
|-
| style="text-align: center;" | 4.0-4.5
| style="text-align: center; background-color: Yellow;" | Supported with 
changes
|-
| style="text-align: center;" | 4.6
| style="text-align: center; background-color: Green;" | Supported
|}

===Framework 2.0-3.5===

No TLS 1.2 support. You must update to at least framework version 4.0


===Framework 4.0===

For ASP.Net 4.0, you can use either of the following two methods to 
enable TLS 1.2 support:

'''NOTE:''' .Net Framework 4.5 or above must be installed for this to 
work. However, your application can still target Framework 4.0.


* Method one - per application support


C# Code:
System.Net.ServicePointManager.SecurityProtocol |= 
(SecurityProtocolType)768 | (SecurityProtocolType)3072;

* Method two - server-wide support via registry change - '''All of our 
shared servers have this enabled'''


UseStrongCrypto.reg file
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001


[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001

OR

Command Prompt (cmd):
reg add HKLM\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 /v 
SchUseStrongCrypto /t REG_DWORD /d 1
reg add HKLM\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319 
/v SchUseStrongCrypto /t REG_DWORD /d 1

OR

PowerShell:
Set-ItemProperty -Path 
HKLM:\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 -Name 
SchUseStrongCrypto -Value 1
Set-ItemProperty -Path 
HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319 -Name 
SchUseStrongCrypto -Value 1


===Framework 4.5===

For ASP.Net 4.5, you can use either of the following two methods to 
enable TLS 1.2 support:

* Method one - per application support


C# Code:
System.Net.ServicePointManager.SecurityProtocol |= 
System.Net.SecurityProtocolType.Tls11 | 
System.Net.SecurityProtocolType.Tls12;

* Method two - server-wide support via registry change - '''All of our 
shared servers have this enabled'''


UseStrongCrypto.reg file
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001


[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001

OR

Command Prompt (cmd):
reg add HKLM\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 /v 
SchUseStrongCrypto /t REG_DWORD /d 1
reg add HKLM\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319 
/v SchUseStrongCrypto /t REG_DWORD /d 1

OR

PowerShell:
Set-ItemProperty -Path 
HKLM:\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 -Name 
SchUseStrongCrypto -Value 1
Set-ItemProperty -Path 
HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319 -Name 
SchUseStrongCrypto -Value 1


===Framework 4.6===

ASP.Net 4.6 supports TLS 1.2 without any changes.