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

i doubt if utls's fingerprint has been detected #321

Open
Nyx2022 opened this issue Dec 13, 2024 · 2 comments
Open

i doubt if utls's fingerprint has been detected #321

Nyx2022 opened this issue Dec 13, 2024 · 2 comments

Comments

@Nyx2022
Copy link

Nyx2022 commented Dec 13, 2024

in some site, when is use utls to imitate browsers like chrome and firefox,but it will has the err:
ReadVersion: expected 'H', got '\x00' at position 0 when receive response
but when i use golang's tls it will not has the error,so i doubt if utls's fingerprint has been detected and be blocked!

@1mike12
Copy link

1mike12 commented Feb 1, 2025

I wonder if utls fingerprint masking has been unmasked

On some sites, when I use uTLS to imitate browsers like Chrome and Firefox, I get the following error:

ReadVersion: expected 'H', got '\x00' at position 0 when receiving a response.

However, when I use Go's native TLS, I do not encounter this error. So, I wonder if uTLS's fingerprint has been detected and blocked.

discussion

Can you tell us which site or at least which cdn is catching it?

Do the fingerprints match when you go to tls.browserleaks.com ?

@jjsaunier
Copy link

Which urls exactly? Because that Looks like more a potential bug in implementation than a detection

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

3 participants