The Redstor platform uses secure ciphers for TLS communications for data protection and management, and also for management purposes to ensure that customer data security is maintained.
The exact details of currently supported ciphers can be found here. The ciphers are selected based on current security standards, and are periodically updated.
The cipher support for the agents is built into the agent software, so is independent of direct communications built into the operating system. Even if the operating system does not support the ciphers directly, the agent will be be able to function (backup and restore).
The ciphers listed are supported on the current Redstor ESE, SE and Cloud agents.
It is important to note that not all operating systems currently supported by the manufacturer are able to support these ciphers to their full extent.
Windows 2012 R2 and earlier, and also Windows 8.1 and earlier, whilst still supported by Microsoft under Extended Support at the time of writing, do not support the full range of secure ciphers in their .Net implementations, which are built into the operating system.
The ciphers TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 and TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 are considered secure where they use a sufficient number of bits, but weak where they do not.
The implementation in Windows 2016 and higher for these ciphers uses sufficient bits for the connection to be secure, whilst 2012 r2 does not.
Although Redstor's testing ahead of the cipher policy change showed that it was possible for Windows 2012 r2 and Windows 8.1 to successfully connect to the Redstor Platform, there is no guarantee that they will be able to do so under all circumstances (eg not able to use sufficient bits to establish a secure connection).
For older operating systems such as Windows 2012 and Windows 2008 r2, these are less likely to be able to use .Net to connect by default.
.Net is used by web browsers, PowerShell, Instant Data and the Storage Platform Console, these tools may be affected if a secure connection cannot be established.
As a workaround, you may be able to implement the secure cipher policy to match the Redstor Platform as found here.
It is recommended to ensure that the server is running on the latest .Net version when applying the policy, and doing so may allow the client to connect successfully.
It is however, important to note the consequences of making this change.
The cipher policy applies to both client and server secure .Net TCP connections, and based on Redstor's testing, is believed to be implemented asymmetrically by Microsoft - the ciphers may be implemented and allowed for client connections, but unavailable for use by server connections on the older OS.
If the operating system does not have any ciphers that it can use for secure .Net server connections (or none that are compatible with peer client ciphers), the user can expect to see a negative impact as secure connections to it will fail.
Redstor cannot be held not responsible for any unexpected consequences to other applications and services (eg secure webserver, secure Remote Desktop Connection) if the cipher suite is updated.
You are strongly advised to confirm that applications and services continue to work as expected.
For product lifecycle reasons, it is almost always preferable to update the operating system to a version that the manufacturer fully supports, thus avoiding the scenario described above.
Windows product lifecycle and support details can be found here: https://docs.microsoft.com/en-us/lifecycle/
Tools such as Python, Java, cURL and other third party tools that do not use the Windows .Net will not be affected by the cipher policy on the machine (whether default or specifically applied), and would be unaffected by changes made to this.
If you are unsure if you are experiencing connectivity issues related to ciphers, please contact Redstor Support using email@example.com.