Search Issue Tracker
Fixed in 2018.2
Unity does not allow to use TLS version higher than 1.0
1. Extract the attached project;
2. In the Certificate Folder are the certificates needed
for the TLS encryption. Copy that folder to
Application.persistentDataPath + "/Certificates/" folder for each project;
Note: Through Wireshark TLS1 is the
only protocol that shows up even if TLS12 is selected. There are two
locations to change this. Roughly Line 203 and line 241.
3. Wireshark must be configured to accept port 20000 as an encrypted port.
Go to Edit > Preferences > Protocols > HTTP and then add 20000 to
the SSL/TLS Ports;
Note: The projects are set up to run on the same computer, however, in order
for Wireshark to detect them it is easier to move the client to a separate
computer and just change the IP in the ConnectToServer function.
4. On Unity, open both projects: EncryptedClient and EncryptedServer and enter Play mode;
5. On Wireshark, capture Network with filter "tcp.port == 20000".
Expected result: Wireshark test shows TLS1.2
Actual result: Unity does not allow to use TLS version higher than 1.0.
Reproduced on versions: 2017.1.0b3, 2017.1.0f3, 2017.2.0b3.
Fixed in: 2018.2.0b1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- New animation clips are not imported correctly when re-importing a fbx file
- Editor freezes when recompiling scrips in Play Mode
- Shuriken particles depth offset is not working(has no affect) when 'Renderer Alignment' is set to 'View'
- [InputSystem] InputSystem is not initialized when run in `-batchmode`
- Assertion failed on expression: 'rs->textureID == realRS->textureID'