HTTPS Decryption (Man-in-the-Middle Attack, MitM)

Surge may decrypt HTTPS traffic by MitM. Please see Wikipedia article for more information.

The certificate generator can help you generate a new CA certificate for debugging and make the certificate trusted by the system. It's available in Surge Dashboard (Mac version) and Surge iOS Config Editor. This certificate is generated locally and only saved in your profile file and the system Keychain. The key of the new certificate is generated randomly using OpenSSL.

You can also use an existing CA certificate. Export the certificate to PKCS#12 format (.p12) with a passphrase. Please note that the passphrase cannot be empty due to system limitations. Use the "base64" command to encode in the base64 string and append these settings below to your config file.

ca-p12 = MIIJtQ.........
ca-passphrase = password
hostname = *
h2 = true

Surge only decrypts traffic to hosts declared here. A general configuration may be like this:

hostname = -*, -*, *

Some applications have a strict security policy to use pinned certificates or CA. Enabling decryption to these hosts may cause problems.

This parameter is of the Host List type, for detailed rules see: Host List Parameter Type


skip-server-cert-verify (Boolean, Default: false)

Do not verify the certificate of the remote host while performing MITM.

h2 (Boolean, Default: false)

MITM over HTTP/2: Decrypt HTTPS traffic with MITM over HTTP/2 protocol, which can improve the performance of concurrent requests.


Use this parameter to enable the MITM function on some devices only.

  • It's a list parameter using commas as the separator.
  • You may specify a single IP address or use a CIDR block. Both IPv4 and IPv6 are supported.
  • You may use the - prefix to exclude some clients, e.g., client-source-address = -,
  • If the parameter is not set, MITM is enabled for all clients. A equivalent to client-source-address =, ::/0
  • should be included if you want to enable MITM for the current device.

auto-quic-block (Boolean, Default: true) iOS 5.8.0+ Mac 5.4.0+

When a QUIC connection (i.e., HTTP/3) hits the MITM hostname list, it automatically blocks that QUIC connection, causing the connection to fall back to HTTP/2 or HTTP/1.1, so that it can be intercepted by MITM.

results matching ""

    No results matching ""