Search Issue Tracker
Fixed in 2021.3.31f1
Fixed in 2021.3.X, 2022.3.X, 2023.1.X, 2023.2.X, 2023.2.0b10, 2023.3.X
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
3. Packet-capturing information provided in internal comments
4. Reproduced with 2020.3 (no longer supported)
Comments (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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Shader warning in 'Hidden/Core/DebugOccluder' thrown after building High Definition 3D Sample Template
- Audio Mixer “+” buttons overlap with UI when the Audio Mixer window layout is set to Horizontal
- "Clear" button in the "Set project display name" closes all the pop-up instead of clearing just a name from the field
- Video Player renders no video on specific devices when using Vulkan
- The Editor slows itself down by showing tons of warnings when the majority of TransformAccessArrays content are NullRefs
Resolution Note (fix version 2023.3):
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.
Resolution Note (fix version 2023.2):
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.
Resolution Note (fix version 2023.1):
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.
Resolution Note (fix version 2022.3):
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.
Resolution Note (fix version 2021.3):
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.