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

it seems ja3 not really get rid of the GREASE #38

Closed
smileboywtu opened this issue May 23, 2019 · 1 comment
Closed

it seems ja3 not really get rid of the GREASE #38

smileboywtu opened this issue May 23, 2019 · 1 comment

Comments

@smileboywtu
Copy link

i have head to https://ja3er.com/ , after some of time , i get another ja3 hash, that's change after a while , i have read this draft document.

my current browser version:
chrome version 74.0.3729.157(64 位)
mac osx 10.11.6

@jalthouse-sfdc
Copy link
Contributor

As Chrome updates itself you may get different JA3 values. Also, Chrome sends an initial JA3 that's always the same but then sends a slightly different one when reconnecting to a server it is already familiar with. For example, see:
66918128f1b9b03303d77c6f2eefd128
e1e178b202995483151741373b7c8c1d
The difference appears to be that ja3er isn't using EC ciphers so on reconnect, chrome doesn't send EC extensions.

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

No branches or pull requests

2 participants