Show HN: A local MitM proxy to control TLS fingerprints

ytkoka 25 points 6 comments August 18, 2026
github.com · View on Hacker News

Discussion Highlights (4 comments)

psanford

There are a bunch of these tools out there. I like curl-impersonate[0] as a quick way to make curl fingerprint as chrome or firefox. There's also CylceTLS[1] for a more programmatic approach. [0]: https://github.com/lwthiker/curl-impersonate [1]: https://github.com/Danny-Dasilva/CycleTLS

Retr0id

I like to use https://github.com/LyleMi/ja3proxy which does exactly the same thing and was first written in the pre-vibe era.

abadwy

Interesting

peter_d_sherman

Interesting indeed! Observation: This, or any tool like this (any proxy which can negotiate an SSL and/or TLS connection) could be used to give simple browsers, browsers that don't implement SSL or TLS natively, SSL and/or TLS capabilities... (In other words, if I were going to write the simplest of all possible Web Browsers, a Web Browser solely for teaching purposes, then I'd intentionally separate its source code from SSL/TLS/encryption code. Why? Well, it would greatly reduce the lines of code in the browser, which would aid greatly in making that source code easier to read/understand. SSL/TLS/Encryption could be implemented in a separate local proxy server, much like the one above, and the simple browser would gain the ability to make SSL/TLS/Encrypted connections through it, while keeping all of that additional code separate... also, on that note, JavaScript processing (all browser code necessary to run JavaScript) could also be separated into it own local server...) So yes, again, very interesting!

Semantic search powered by Rivestack pgvector
4,128 stories · 37,281 chunks indexed