Skip to content

Commit 1016538

Browse files
Transport Layer Security (TLS) Version Support
1 parent ba34624 commit 1016538

File tree

1 file changed

+21
-0
lines changed

1 file changed

+21
-0
lines changed

src/pages/docs/channels/options/encryption.mdx

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -36,6 +36,27 @@ Unencrypted communication with Ably is **disallowed** if any of the following co
3636

3737
* A client using an unencrypted connection attempts to attach to a channel that is configured to be used with [TLS only](/docs/channels#rules).
3838

39+
### TLS version support
40+
41+
Ably endpoints support TLS 1.2 and TLS 1.3, providing modern, secure encryption methods that protect your data and communications from malicious attacks.
42+
43+
**Automatic version negotiation:**
44+
Ably automatically defaults to the highest TLS version supported by both the client and server. If both support TLS 1.3, it will be used by default as it provides the most secure and efficient connection.
45+
46+
Benefits of TLS 1.2 and 1.3:
47+
- Protection against vulnerabilities such as man-in-the-middle attacks.
48+
- TLS 1.3 reduces round trips during handshake for quicker connections.
49+
- Forward secrecy and improved encryption algorithms.
50+
- Modern environments support these versions by default.
51+
52+
#### Legacy TLS versions
53+
54+
TLS 1.0 and 1.1 are deprecated and [will be sunset in June 2025](/docs/platform/deprecate/tls-v1-1). These older versions pose security risks and should be avoided. If using legacy systems, update them to support TLS 1.2 or higher.
55+
56+
#### Client configuration
57+
58+
Most modern clients and libraries are configured automatically to use TLS 1.2+ by default. The JavaScript library uses the TLS version supported by the browser environment, while Node.js uses the version determined by the Node.js runtime.
59+
3960
### TLS vs. message encryption
4061

4162
While TLS encryption ensures that messages in transit to and from Ably cannot be intercepted, inspected, or tampered with, it does not ensure that the Ably service itself is unable to inspect your messages and their content. If you want to ensure that all messages are encrypted and inaccessible to even Ably, consider using the [message-level encryption](#with-ably) feature included in the client libraries.

0 commit comments

Comments
 (0)