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

Fix Google Parrots #125

Merged
merged 2 commits into from
Oct 12, 2022
Merged

Fix Google Parrots #125

merged 2 commits into from
Oct 12, 2022

Conversation

gaukas
Copy link
Contributor

@gaukas gaukas commented Oct 12, 2022

  • Move HelloChrome_102 to the end of HelloChrome_ fingerprints for consistency.
  • Fixed Chrome 98+ Fingerprint Mismatch #123 by adjusting mismatching SupportedVersionsExtension value in HelloChrome_100.

- Move `HelloChrome_102` to the end of `HelloChrome_` fingerprints for consistency.
- Fixed #123 by adjusting mismatching SupportedVersionsExtension value in `HelloChrome_100`.
@gaukas
Copy link
Contributor Author

gaukas commented Oct 12, 2022

Even with the above patch, Chrome 100's fingerprint doesn't look right. Either way will not be well-known to tlsfingerprint.io.

According to https://tlsfingerprint.io/id/e47eae8f8c4887b6, Chrome 100 appears to use the same fp with 102+.

According to [TLSFingerprint.io: id e47eae8f8c4887b6](https://tlsfingerprint.io/id/e47eae8f8c4887b6), Chrome 100 may share this fp with 102.
@gaukas gaukas merged commit 35e5b05 into master Oct 12, 2022
@gaukas gaukas deleted the fix-chrome-parrot branch October 28, 2022 02:14
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 this pull request may close these issues.

Chrome 98+ Fingerprint Mismatch
1 participant