Conversation
0x676e67
force-pushed
the
emulate
branch
3 times, most recently
from
a837dde to
bd9d14e
Compare
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
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.
It now supports parsing Chrome profiles. You can obtain configurations either by manual editing or deploying the request endpoint from https://github.com/pagpeter/TrackMe. We currently only adopt its format since it supports PSK, while https://tls.browserleaks.com/ does not.
Calculation algorithms like JA3 and JA4 are not critical here; they are merely statistical hashes and cannot truly reflect real Chrome fingerprints. For newer versions, set
permute_extensions: trueto enable random extension shuffling.