Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chrome 98+ Fingerprint Mismatch #123

Closed
gaukas opened this issue Oct 12, 2022 · 0 comments · Fixed by #125
Closed

Chrome 98+ Fingerprint Mismatch #123

gaukas opened this issue Oct 12, 2022 · 0 comments · Fixed by #125

Comments

@gaukas
Copy link
Member

gaukas commented Oct 12, 2022

Sorry to weigh in late on this, but the Chrome signature for 98+ is a tiny bit wrong. They changed in Chrome 98 to only include tls versions 1.3 and 1.2. They removed 1.1 and 1.0. Here's a link to the signature:
ulixee@e8f6488

We have a suite that automates testing tls signatures across browsers and operating systems here, if it's of use:
test suite: https://github.com/unblocked-web/double-agent/tree/41489d6f260cc3861574a0f606e99d04b3bfe799
data: https://github.com/unblocked-web/browser-profile-data/tree/main/profiles

Originally posted by @blakebyrnes in #122 (comment)

gaukas added a commit that referenced this issue Oct 12, 2022
- Move `HelloChrome_102` to the end of `HelloChrome_` fingerprints for consistency.
- Fixed #123 by adjusting mismatching SupportedVersionsExtension value in `HelloChrome_100`.
gaukas added a commit that referenced this issue Oct 12, 2022
* Fix Google Parrots

- Move `HelloChrome_102` to the end of `HelloChrome_` fingerprints for consistency.
- Fixed #123 by adjusting mismatching SupportedVersionsExtension value in `HelloChrome_100`.

* Use same fp for Chrome 100 and 102

According to [TLSFingerprint.io: id e47eae8f8c4887b6](https://tlsfingerprint.io/id/e47eae8f8c4887b6), Chrome 100 may share this fp with 102.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant