feat: add factory for TLS proxying with uTLS (v3) #22
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 commit build upon 475e580 to allow users to optionally specify the TLSClientFactory to use on a per-Transport basis. If the transport TLSClientFactory isn't set, we'll default to using the global TLSClientFactory. While working on this diff, I realized that, for the common use case, a user doesn't need to override DialTLSContext and they can just set the global or per-transport TLSClientFactory in order to use their uTLS fingerprint of choice.
bassosimone
force-pushed
the
tls-factory-v3
branch
from
17d2b34
to
2583538
Compare
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 commit build upon 475e580 to
allow users to optionally specify the TLSClientFactory to use on
a per-Transport basis. If the transport TLSClientFactory isn't set,
we'll default to using the global TLSClientFactory.
While working on this diff, I realized that, for the common use
case, a user doesn't need to override DialTLSContext and they can
just set the global or per-transport TLSClientFactory in order
to use their uTLS fingerprint of choice.