TLS 1.2 Enabled registry value-"0xffffffff" 0r 1

%3CLINGO-SUB%20id%3D%22lingo-sub-324275%22%20slang%3D%22en-US%22%3ETLS%201.2%20Enabled%20registry%20value-%220xffffffff%22%200r%201%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-324275%22%20slang%3D%22en-US%22%3E%3CP%3ECould%20you%20please%20confirm%20what%20should%20be%20the%20correct%26nbsp%3BTLS%201.2%20%22Enabled%22%20registry%20value-%220xffffffff%22%200r%201.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThere%20are%20multiple%20articles%20in%20internet%20that%20refer%20to%20each%20one%20of%20these.%20Does%20%220xffffffff%22%20value%20performs%20same%20function%20as%20decimal%20value%201%3F%20Is%20this%20the%20OS%20Default%20value%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20exchange%202010%2F2013%20servers.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-324275%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-324285%22%20slang%3D%22en-US%22%3ERe%3A%20TLS%201.2%20Enabled%20registry%20value-%220xffffffff%22%200r%201%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-324285%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fsecurity%2Ftls%2Ftls-registry-settings%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fsecurity%2Ftls%2Ftls-registry-settings%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3ETo%20enable%20the%20TLS%201.2%20protocol%2C%20create%20an%20Enabled%20entry%20in%20either%20the%20Client%20or%20Server%20subkey%20as%20described%20in%20the%20following%20table.%20This%20entry%20does%20not%20exist%20in%20the%20registry%20by%20default.%20After%20you%20have%20created%20the%20entry%2C%20change%20the%20DWORD%20value%20to%201.%3CBR%20%2F%3E%3CBR%20%2F%3EHope%20that%20helps%3CBR%20%2F%3E%3CBR%20%2F%3EBest%2C%20Chris%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1131795%22%20slang%3D%22en-US%22%3ERe%3A%20TLS%201.2%20Enabled%20registry%20value-%220xffffffff%22%200r%201%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1131795%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F169605%22%20target%3D%22_blank%22%3E%40Christopher%20Hoard%3C%2FA%3E%26nbsp%3Bit%20is%20not%20100%25%20sure%20that%20it%20is%20a%20value%20of%201.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHave%20a%20look%20under%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdotnet%2Fframework%2Fnetwork-programming%2Ftls%3FWT.mc_id%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdotnet%2Fframework%2Fnetwork-programming%2Ftls%3FWT.mc_id%3C%2FA%3E%3C%2FP%3E%3CH2%20id%3D%22toc-hId-1850587040%22%20id%3D%22toc-hId-1850587062%22%20id%3D%22toc-hId-1850587062%22%20id%3D%22toc-hId-1850587062%22%3EConfiguring%20Schannel%20protocols%20in%20the%20Windows%20Registry%3C%2FH2%3E%3CP%3EYou%20can%20use%20the%20registry%20for%20fine-grained%20control%20over%20the%20protocols%20that%20your%20client%20and%2For%20server%20app%20negotiates.%20Your%20app's%20networking%20goes%20through%20Schannel%20(which%20is%20another%20name%20for%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fdesktop%2FSecAuthN%2Fsecure-channel%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3ESecure%20Channel%3C%2FA%3E.%20By%20configuring%20Schannel%2C%20you%20can%20configure%20your%20app's%20behavior.%3C%2FP%3E%3CP%3EStart%20with%20the%20HKEY_LOCAL_MACHINE%5CSYSTEM%5CCurrentControlSet%5CControl%5CSecurityProviders%5CSCHANNEL%5CProtocols%20registry%20key.%20Under%20that%20key%20you%20can%20create%20any%20subkeys%20in%20the%20set%20SSL%202.0%2C%20SSL%203.0%2C%20TLS%201.0%2C%20TLS%201.1%2C%20and%20TLS%201.2.%20Under%20each%20of%20those%20subkeys%2C%20you%20can%20create%20subkeys%20Client%20and%2For%20Server.%20Under%20Client%20and%20Server%2C%20you%20can%20create%20DWORD%20values%20DisabledByDefault%20(0%20or%201)%20and%20Enabled%20(0%20or%200xFFFFFFFF).%3CBR%20%2F%3E%3CBR%20%2F%3EI%20know%20that%20your%20article%20is%20newer%20but%20at%20the%20end%20I%20think%20it%20makes%20not%20a%20difference%20if%20you%20try%200xffffffff%20or%20use%20a%201.%3C%2FP%3E%3CP%3EBest%20regards%3C%2FP%3E%3CP%3ERoger%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2014464%22%20slang%3D%22en-US%22%3ERe%3A%20TLS%201.2%20Enabled%20registry%20value-%220xffffffff%22%200r%201%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2014464%22%20slang%3D%22en-US%22%3EI%20think%20I%20would%20point%20out%20for%20anyone%20who%20reads%20this%20later%20that%20the%20article%20cited%20above%20has%20since%20been%20updated%20to%20match%20the%20Windows%20Server%20SCHANNEL%20registry%20guidelines.%20To%20enable%2C%20set%20the%20Enabled%20key%20to%201%2C%20to%20disable%2C%20set%20Enabled%20key%20to%200.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdotnet%2Fframework%2Fnetwork-programming%2Ftls%3FWT.mc_id%23configuring-schannel-protocols-in-the-windows-registry%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdotnet%2Fframework%2Fnetwork-programming%2Ftls%3FWT.mc_id%23configuring-schannel-protocols-in-the-windows-registry%3C%2FA%3E%3CBR%20%2F%3EConfiguring%20Schannel%20protocols%20in%20the%20Windows%20Registry%3CBR%20%2F%3EYou%20can%20use%20the%20registry%20for%20fine-grained%20control%20over%20the%20protocols%20that%20your%20client%20and%2For%20server%20app%20negotiates.%20Your%20app's%20networking%20goes%20through%20Schannel%20(which%20is%20another%20name%20for%20Secure%20Channel.%20By%20configuring%20Schannel%2C%20you%20can%20configure%20your%20app's%20behavior.%3CBR%20%2F%3E%3CBR%20%2F%3EStart%20with%20the%20HKEY_LOCAL_MACHINE%5CSYSTEM%5CCurrentControlSet%5CControl%5CSecurityProviders%5CSCHANNEL%5CProtocols%20registry%20key.%20Under%20that%20key%20you%20can%20create%20any%20subkeys%20in%20the%20set%20SSL%202.0%2C%20SSL%203.0%2C%20TLS%201.0%2C%20TLS%201.1%2C%20and%20TLS%201.2.%20Under%20each%20of%20those%20subkeys%2C%20you%20can%20create%20subkeys%20Client%20and%2For%20Server.%20Under%20Client%20and%20Server%2C%20you%20can%20create%20DWORD%20values%20DisabledByDefault%20(0%20or%201)%20and%20Enabled%20(0%20or%201)%3C%2FLINGO-BODY%3E
Occasional Contributor

Could you please confirm what should be the correct TLS 1.2 "Enabled" registry value-"0xffffffff" 0r 1.

 

There are multiple articles in internet that refer to each one of these. Does "0xffffffff" value performs same function as decimal value 1? Is this the OS Default value?

 

We have exchange 2010/2013 servers.

4 Replies
https://docs.microsoft.com/en-us/windows-server/security/tls/tls-registry-settings

To enable the TLS 1.2 protocol, create an Enabled entry in either the Client or Server subkey as described in the following table. This entry does not exist in the registry by default. After you have created the entry, change the DWORD value to 1.

Hope that helps

Best, Chris

@Christopher Hoard it is not 100% sure that it is a value of 1.

 

Have a look under 

 

https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls?WT.mc_id

Configuring Schannel protocols in the Windows Registry

You can use the registry for fine-grained control over the protocols that your client and/or server app negotiates. Your app's networking goes through Schannel (which is another name for Secure Channel. By configuring Schannel, you can configure your app's behavior.

Start with the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols registry key. Under that key you can create any subkeys in the set SSL 2.0, SSL 3.0, TLS 1.0, TLS 1.1, and TLS 1.2. Under each of those subkeys, you can create subkeys Client and/or Server. Under Client and Server, you can create DWORD values DisabledByDefault (0 or 1) and Enabled (0 or 0xFFFFFFFF).

I know that your article is newer but at the end I think it makes not a difference if you try 0xffffffff or use a 1.

Best regards

Roger

 

I think I would point out for anyone who reads this later that the article cited above has since been updated to match the Windows Server SCHANNEL registry guidelines. To enable, set the Enabled key to 1, to disable, set Enabled key to 0.

https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls?WT.mc_id#configuring-schan...
Configuring Schannel protocols in the Windows Registry
You can use the registry for fine-grained control over the protocols that your client and/or server app negotiates. Your app's networking goes through Schannel (which is another name for Secure Channel. By configuring Schannel, you can configure your app's behavior.

Start with the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols registry key. Under that key you can create any subkeys in the set SSL 2.0, SSL 3.0, TLS 1.0, TLS 1.1, and TLS 1.2. Under each of those subkeys, you can create subkeys Client and/or Server. Under Client and Server, you can create DWORD values DisabledByDefault (0 or 1) and Enabled (0 or 1)

@nmyron3983  I was trying to understand what that hex value represented since their current guidance doesn't reflect it. You just saved me a lot of searching, thanks!