Search Issue Tracker

Fixed

Fixed in 2021.3.31f1, 2022.3.10f1, 2023.1.13f1, 2023.2.0b10, 2023.3.0a5

Votes

1

Found in

2021.3.27f1

2022.3.4f1

2023.1.2f1

2023.2.0a21

Issue ID

UUM-41557

Regression

No

UnityWebRequest uses TLSv1 protocol during TLS handshake instead of TLSv1.2 protocol when calling the UnityWebRequest.Get method

--

-

How to reproduce:
1. Open the “UnityWebRequestTLS12_2022“ project
2. Open the “SampleScene”
3. Open a packet-capturing software and start capturing packets
4. Enter Play Mode
5. Exit Play Mode, stop capturing packets, and observe the packets that were sent with packet-capturing software

Expected result: TLSv1.2 protocol packets are sent
Actual result: TLSv1 protocol packets are sent

Reproduced with: 2021.3.27f1, 2022.3.4f1, 2023.1.2f1, 2023.2.0a21

Reproduced on: Windows 10 (by reporter), Windows 11

Notes:
1. Also reproduced in Player
2. Latest 2022.3 LTS Stream documentation mentions that TLS 1.2 is supported and has been added since 2018.3 stream: [https://docs.unity3d.com/2022.3/Documentation/Manual/dotnetProfileSupport.html|https://docs.unity3d.com/2022.3/Documentation/Manual/dotnetProfileSupport.html|smart-link]
3. Packet-capturing information provided in internal comments
4. Reproduced with 2020.3 (no longer supported)

  1. Resolution Note (fix version 2023.3.0a5):

    Issue was caused by a recent update to our TLS library that disabled SHA-1 signature hashes But this is the only signature hash supported by Windows Server 2012 and 2016, so this caused a regression as new TLS sessions would now fail to be established. The fix was to re-enable SHA-1 signature hashes.

  2. Resolution Note (fix version 2023.2.0b10):

    Issue was caused by a recent update to our TLS library that disabled SHA-1 signature hashes But this is the only signature hash supported by Windows Server 2012 and 2016, so this caused a regression as new TLS sessions would now fail to be established. The fix was to re-enable SHA-1 signature hashes.

  3. Resolution Note (fix version 2023.1.13f1):

    Issue was caused by a recent update to our TLS library that disabled SHA-1 signature hashes But this is the only signature hash supported by Windows Server 2012 and 2016, so this caused a regression as new TLS sessions would now fail to be established. The fix was to re-enable SHA-1 signature hashes.

  4. Resolution Note (fix version 2022.3.10f1):

    Issue was caused by a recent update to our TLS library that disabled SHA-1 signature hashes But this is the only signature hash supported by Windows Server 2012 and 2016, so this caused a regression as new TLS sessions would now fail to be established. The fix was to re-enable SHA-1 signature hashes.

  5. Resolution Note (fix version 2021.3.31f1):

    Issue was caused by a recent update to our TLS library that disabled SHA-1 signature hashes But this is the only signature hash supported by Windows Server 2012 and 2016, so this caused a regression as new TLS sessions would now fail to be established. The fix was to re-enable SHA-1 signature hashes.

Comments (1)

  1. FunRobDev

    Aug 05, 2023 09:50

    Please fix this one, because UnityWebRequest does not work with Windows Server 2012, nor Windows Server 2016, when using https / TLS. The last working version was in Unity 2019.x

Add comment

Log in to post comment