[GH-ISSUE #586] TLS Fingerprint #473

New issue

Open

opened 2026-02-27 23:17:01 +03:00 by kerem · 1 comment

kerem commented

2026-02-27 23:17:01 +03:00

Owner

Originally created by @GunGunGun on GitHub (Oct 5, 2025).
Original GitHub issue: https://github.com/snail007/goproxy/issues/586

Currently TLS Fingerprint is widely implemented on most serverside, which makes using MITM proxy ways harder than before, do we have any counter measure for this problem, currently uTLS is being used to bypass them, pretty much perfect solution without any downside.

Originally created by @GunGunGun on GitHub (Oct 5, 2025). Original GitHub issue: https://github.com/snail007/goproxy/issues/586 Currently TLS Fingerprint is widely implemented on most serverside, which makes using MITM proxy ways harder than before, do we have any counter measure for this problem, currently uTLS is being used to bypass them, pretty much perfect solution without any downside.

kerem commented

2026-02-27 23:17:03 +03:00

Author

Owner

@snail007 commented on GitHub (Oct 8, 2025):

The TLS handshake is between the client and the target server. Goproxy is just a pure forwarding at the TCP level and does not analyze or modify TLS communication. The TLS fingerprint you mentioned is also determined by the client.

@snail007 commented on GitHub (Oct 8, 2025): The TLS handshake is between the client and the target server. Goproxy is just a pure forwarding at the TCP level and does not analyze or modify TLS communication. The TLS fingerprint you mentioned is also determined by the client.