SendSafely Service Notification Regarding TLS

Posted on 11/15/2019

On December 15, 2019 SendSafely will be phasing out support for older versions of the TLS encryption protocol. We encourage you to review the information below to determine whether you may be affected by this change, along with the recommended steps to avoid any impact. 

TLS v1.0 and v1.1 connections will be disabled according to the following timeline: 

• December 15, 2019 - Disable support for TLS 1.0 on API and Browser connections
• February 15, 2020 - Disable support for TLS 1.1 on API and Browser connections

After this change, TLS 1.2 encryption or higher will be required to connect to SendSafely services. 

 

How to tell if you are affected

 

Most modern web browsers already support TLS 1.2 encryption, so as long as users are running an up to date browser and operating system they should not be impacted by this change.

The only users likely to be affected would be those that access SendSafely outside of the web browser, such as through our Outlook Plug-in, one of our command line utilities or a custom API integration. 

 

Outlook Plug-In 

The vast majority of SendSafely Outlook users run the ClickOnce version of our Outlook plug-in. This version of the plug-in automatically updates when new releases are available. All users that are running the ClickOnce version of our plug-in will receive an update over the coming weeks that will ensure they are not affected by this change. These users will not be affected.

 

Users that installed the Outlook Plug-in using our Standalone (Offline) MSI Installer may need to manually apply an update to ensure that their plug-in is updated to the most recent version. SendSafely has already notified users that were previously provided access to that version of the plug-in with instructions on how to install the required update. 

 

If you believe you may have users who are running the Standalone (Offline) MSI version of our Outlook Plug-in and have not already been contact by our support team, please consult this Help Center article that outlines the step you should take. 

 

Command Line Utilities

SendSafely command line utilities, such as our Package Export Utility and the SendSafely Command Line Utility (CLI) for Windows, may need to be updated in order to ensure compatibility with TLS 1.2. If you use one of these utilities, we encourage you to download the most recent version of each using the links below:

• Package Export Utility (v1.3)
• SendSafely CLI for Windows (v1.4)

 

Custom API Integrations 

If you have developed a custom SendSafely API integration that uses one of our SendSafely Client Libraries for Java or .NET, we encourage you to check your integration to ensure it is deployed in a manner where TLS 1.2 is supported. 

 

Windows Client API

• Integrations running on Microsoft .NET Framework v4.6 or later will automatically support TLS 1.2. 

• Integrations running on Microsoft .NET Framework v4.5 will need to use our most recent Windows Client API package (v3.0.4), which is available here.

• Integrations that run on older versions of the Microsoft .NET Framework WILL NOT support TLS 1.2 and will require an upgrade.

 

Java Client API

• Integrations that run on Java 8 or higher will automatically support TLS 1.2.  

• Integrations that run on Java 6 or Java 7 WILL NOT support TLS 1.2 and will require an upgrade. 

If you have any additional questions or need assistance making sure that you will not be impacted by this change, please open a case with our Support Team by emailing [e-mail].