TLS handshake timeout (Fix #37) #39
Merged
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 was referenced Jan 16, 2024
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 PR adds a timeout to the TLS handshake, to guard against TCP connection leaks arising from poor connections or malicious activity. This type of connection leak can seriously impair an internet-facing server (I know from experience). A test case is included to verify the functionality works.
The downside is that a https://docs.rs/tokio/latest/tokio/time/struct.Sleep.html is required per connection being accepted, which I believe is a heap allocation.
Please note: This PR is on top of my
AddrIncomingConfigPR (#38), for my own convenience, so I can use both together until one or both are merged.