- Man-in-the-middle TLS connections
- Mimic TLS records from the client
- Directly proxy all application data below TLS (for example, http2 frames will be exactly what the client sends)
- SSL/TLS Keylog support (inspect TLS contents in wireshark)
- Certificate server at
utlsproxy.ws(certificates are created locally)
$ go install github.com/saucesteals/utlsproxy$ utlsproxy
-addr string
Address to bind to (default ":8080")
-keylog string
TLS key log file
-http1
Force HTTP/1.1 between client and proxyAll (to my knowledge) MITM proxies replay requests to servers with stdlib transports, essentially letting the server fingerprint it. The goal of utlsproxy is to allow you to inspect TLS application data while mimicking the original client. The proxy will sniff the client's clienthello message and use it as its own when handshaking with the server.
Curious how? Most of the work is at saucesteals/goproxy (credits to elazarl/goproxy for the base proxy implementation)
Like every other MITM, this will not work with mTLS. Find the client's certificate and private key, then add it to the tls.Config (Rarely will you need this, so this is only possible by cloning and adding it yourself)
Contributions are welcome!
Distributed under the GNU GPL v3.0 License. See LICENSE for more information.