-
Notifications
You must be signed in to change notification settings - Fork 252
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 107 started shuffling extensions #132
Comments
We may want to implement Extension shuffler for this. |
If anyone observed the same, please upvote this. For now I have difficulties reproduce it on any other devices/setups. Therefore I am reluctant to get this merged -- perhaps my user error. |
https://tlsfingerprint.io/id/e47eae8f8c4887b6 no change after chrome 106 upgrade to 107.0.5304.107 |
Yep. It is definitely not generalized yet. So far I have only observed this on two Windows11 machines out of 100+ machines I surveyed. That's a major reason why I am holding the PR implementing it. |
See the announcement here |
Ah nice. Thanks @bemasc that's what I've been looking for! |
An incomplete list of possible fingerprints used by Chrome 107:
4c7826a590831f89
54609dcb6ddbf977
66bbe813f85045d4
1a84ca827ce68206
f4bc6fabac86598a
Observation indicates the extensions are getting shuffled with every new Client Hello.
To be honest, this kinda defeats the purpose of uTLS (in terms of parroting).
But I see this as a huge success of uTLS!
The text was updated successfully, but these errors were encountered: