Skip to content

SFTP Security Upgrade

Important security update for SFTP server configurations.

Action Required

If your SFTP server uses the deprecated diffie-hellman-group14-sha1 Key Exchange algorithm, you may experience connectivity issues with RingCentral Archiver. Please follow the instructions below to update your server configuration.

Overview

RingCentral has upgraded its SFTP client software to align with modern cryptographic standards. This update enhances the security of file transfers by deprecating older, less secure Key Exchange algorithms.

The Issue

Our SFTP client has been updated to comply with current security protocols. During connectivity tests, we identified that some SFTP servers are configured to use the diffie-hellman-group14-sha1 algorithm, which is now deprecated due to known SHA-1 vulnerabilities.

As a result, RingCentral's security policy prevents connections to servers using only this deprecated algorithm, which may disrupt automated file transfers.

We recommend enabling the following industry-standard Key Exchange algorithms in your SSH configuration (sshd_config):

Algorithm Priority Notes
ecdh-sha2-nistp256 Recommended Modern, fast, and secure
diffie-hellman-group-exchange-sha256 Strong Fallback Widely supported
diffie-hellman-group14-sha256 Secure Upgrade to legacy group14

Alternative Solutions

If immediate server upgrades are not possible, consider switching to another cloud storage option as a temporary workaround:


Technical Guide: Upgrading OpenSSH Server

This section details the steps required to upgrade an OpenSSH/SFTP server to support modern Key Exchange (KEX) algorithms.

Prerequisites

  • Root/Sudo Access: You must have administrative privileges on the server.
  • Connection Safety: It is highly recommended to keep your current SSH session open and open a secondary session to perform the work. This prevents lockout in case of configuration errors.

Step 1: Diagnose Server Version

Before modifying configurations, ensure the OpenSSH version is capable of supporting modern algorithms.

Run the following command on the server:

ssh -V

Version Analysis:

OpenSSH Version Compatibility
7.4+ Fully supports modern algorithms. Proceed to Step 2.
< 7.4 May support some algorithms, but an OS-level package update is recommended.
< 6.0 Too old. You must upgrade the openssh-server package via yum, apt, or dnf before proceeding.

Step 2: Configure sshd_config

The goal is to explicitly allow modern algorithms while maintaining backward compatibility for legacy clients if necessary.

1. Backup the existing configuration:

sudo cp /etc/ssh/sshd_config /etc/ssh/sshd_config.bak

2. Edit the configuration file:

sudo nano /etc/ssh/sshd_config

3. Update Key Exchange Algorithms:

Locate the KexAlgorithms line. If it does not exist, add it to the end of the file. If it does exist, replace it or append the following values.

Recommended Configuration String:

KexAlgorithms ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1

Algorithm Breakdown:

Algorithm Description
ecdh-sha2-nistp256 / nistp384 / nistp521 Modern, fast, and secure (Preferred by new clients)
diffie-hellman-group-exchange-sha256 Strong standard fallback
diffie-hellman-group14-sha256 Secure upgrade to the legacy group14
diffie-hellman-group14-sha1 (Legacy) Retained at the end to ensure older devices can still connect

Step 3: Apply and Verify Changes

1. Test Configuration Syntax:

Always run this command before restarting to ensure there are no typos:

sudo sshd -t

Tip

If no output is returned, the syntax is valid.

2. Restart SSH Service:

sudo systemctl restart sshd
sudo service sshd restart

3. Verify the Configuration:

From a remote machine (the client), scan the server to confirm it now offers the new algorithms:

ssh -vvv user@<your-server-ip>

Look for the debug line: debug2: peer server KEXINIT proposal. It should now list ecdh-sha2-nistp256 and other algorithms defined in Step 2.


Need Help?

If you have questions or need assistance with this upgrade, please contact RingCentral Support or reach out to your IT administrator for server-specific configurations.


  • Connect SFTP


    Set up your SFTP connection with RingCentral Archiver.

    Connection Guide

  • Alternative Storage


    Explore other cloud storage options if SFTP upgrade isn't possible.

    Storage Options