Impersonate Chrome 110 #148
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
Chrome 110 is already out, so change the new Chrome 109 support with TLS extension permutation to Chrome 110. Also add testing support for permuted TLS extensions.
Closed
|
@lwthiker it will be helpful for us, if you can describe in detail how to use this library with node-libcurl🙂 |
|
There's not test file as well |
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.
Chrome 110 is out, and uses TLS extension permutation enabled by default. See https://chromestatus.com/feature/5124606246518784. This means that the TLS extension order is randomized in each TLS client hello message.
This PR is based on #142. Since Chrome 110 is already out, the Chrome 109 signature was upgraded to Chrome 110.