Important Update for UnityTLS

Hi Unity Developers,

We are introducing an update to UnityTLS, which both Transport and UnityWebRequest depend on, to ensure a more secure networking experience. This update will remove support for the deprecated TLS 1.0 and TLS 1.1 protocols, which are no longer considered secure.

Unity Versions:

This change applies to the next Unity 2021LTS, 2022LTS, and Unity 6 versions as well as all future versions.

What’s Changing:

The minimum supported version of TLS in UnityTLS will be 1.2. The changes will not impact the surface API.

Who Is Affected:

Most users will not be impacted as TLS 1.0 and TLS 1.1 have been deprecated for years.

If you are connecting to servers that only support TLS 1.0 or TLS 1.1, this will be a breaking change as the client will no longer be able to connect to the server.

What to do:

The changes do not impact the surface API so there is no action needed for your Unity client.

14 Likes

Is Unity any closer to supporting TLS 1.3? The content management system we use to communicate with our software is moving to 1.3. .Net Framework that Unity is on supports it, and with the deprecation of 1.0 and 1.1, it seems time to expand to 1.3.

Alternatively, what would be Unity’s recommended approach for dealing with this? There doesn’t appear to be a TLS 1.3 solution in the asset store, and there don’t appear to be clear pathways from the user end on making UnityWebRequest 1.3 compatible.

Hi @AndrewRoto

Thank you for raising this. We do plan to support TLS 1.3 in the coming year as it is on our roadmap. We can’t share specific dates yet however we will update this thread when we release support for it.

-Carlo

1 Like