Add support for TLS 1/1.2/1.3 in redirector #4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This fixes the `IOException: Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host.` error upon starting ME3 (Same issue as described [here](https://me3tweaks.com/forums/viewtopic.php?f=10&t=58). This is after re-enabling SSL3 in the "Internet Options" dialog, and enabling the required ciphers through PowerShell. Ran into it on 64-bit Windows 10, build 1803, with .NET 4.7.3 (I think), connecting to a server running on the same machine, listening on a WiFi interface. Everything works beautifully after changing this line.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes the
IOException: Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host.error upon starting ME3 (Same issue as described here). This is after re-enabling SSL3 in the "Internet Options" dialog, and enabling the required ciphers through PowerShell.Ran into it on 64-bit Windows 10, build 1803, with .NET 4.7.3 (I think), connecting to a server running on the same machine, listening on a WiFi interface.
Everything works beautifully after changing this line.