Add support for TLS enabled servers #54
Open
Conversation
This file contains hidden or 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
Contributor
Author
|
Related, I had some thoughts on how servers might communicate to tracker clients that TLS is available: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Hey Dustin 👋,
I've added TLS support to the latest Mobius release and with the changes in this PR, it seems to be working with your client!
TLS can be enabled with this new toggle in the server connect and bookmark views:
When enabled, transactions and file transfers go through the TLS encrypted connections.
I'm currently running TLS on mobius.trtphotl.com:5600 with a valid Let's Encrypt certificate if you'd like to test it out.
I need to test out some of the unhappy path scenarios (e.g. invalid cert), but I wanted to share this seemingly working implementation! 🎉