Enable TLS 1.2 / Strong Crypto in Windows .net Player

[alex]

By default, the Windows .net Player uses the standard crypto libraries provided by the Microsoft .net Framework.

If you need to use a CMS that provides only TLS 1.2 connections, then you will need to ensure you set the following registry settings:

32 bit machines

Key: HKLM\SOFTWARE\Microsoft\.NetFramework\v4.0.30319\SchUseStrongCrypto
Type: DWORD
Value: 1

64 bit machines

Key: HKLM\SOFTWARE\Wow6432Node\Microsoft\.NetFramework\v4.0.30319\SchUseStrongCrypto
Type: DWORD
Value: 1

Original post that describes this can be found here - with thanks to @Jeremy_Sippel:

Xibo 1.7.8 Windows Client challenges - TLS 1.2?

Awesome- thank you so much as I would probably never teased this out! Enabling strong crypto for .NET was all we needed to do. As kloostec mentioned, we’ve tweaked our httpd services to bump up the security. As most browsers are happy with those tweaks it didn’t occur to us to check (or that .NET did it’s own thing). Specifically, via powershell we did: set strong cryptography on 64 bit .Net Framework (version 4 and above) Set-ItemProperty -Path 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NetFr…