Trim down the InsecureConnection to a minimal implementation.
#23
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 exposes the same API as before, but uses no mock-TLS-like infrastructure that might look more secure than it is. The intention is to help the subsequent actual-TLS PR land more cleanly.
365f77e to
54f3ba7
Compare
4 tasks
eoger
approved these changes
Jan 22, 2019
|
👍 |
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 exposes the same API as before, but uses no mock-TLS-like infrastructure that might look more secure than it is. The intention is to help the subsequent actual-TLS PR land more cleanly, since it will be a suite of entirely new files rather than diffs to existing "mock" files.