Performing a Registry Change for Ares Client or Server to Enable TLS 1.2

Follow
Product:      Ares
Version:       4.6

Problem/Question

Some secure sites (e.g., gpo.gov) will not permit admittance to the website through Ares searches unless you have Transport Layer Security (TLS) 1.2 and a “supported” Secure Sockets Layer (SSL) certificate. When an HTTPS request is being sent by the link checker, older protocols of SSL3 and TLS1.0 are being sent over which is causing links to come back as failed even though they are active websites.

Cause 

  • Websites such as gpo.gov have disabled what they consider insecure security protocols (e.g., SSL3 and TLS 1.0).
  • The security protocol TLS 1.2 is not currently supported by Ares version 4.6.

Resolution

Ares 4.6 was built on .NET Framework 4.5 which supports TLS version 1.0 by default. The .NET Framework 4.5 can be forced to handle TLS 1.1-1.2 by applying a registry change. 

Click on the button below to download the PowerShell script that will perform the registry change. After implementing the changes, restart the Ares System Manager.

Use caution when running this script as the registry change will affect all applications on the server and the client, including non-Atlas applications, built on .NET Frameworks 4.0 and greater.

Registry Change Download

 

 

 

Questions?

If this article didn’t resolve your issue, please take a moment and answer a few questions to help improve our documentation:

Feedback