2013-01-02 08:57:39 +00:00
|
|
|
When mitmproxy receives a connection destined for an SSL-protected service, it
|
|
|
|
|
freezes the connection before reading its request data, and makes a connection
|
|
|
|
|
to the upstream server to "sniff" the contents of its SSL certificate. The
|
|
|
|
|
information gained - the __Common Name__ and __Subject Alternative Names__ - is
|
|
|
|
|
then used to generate the interception certificate, which is sent to the client
|
|
|
|
|
so the connection can continue.
|
2012-04-03 23:24:58 +00:00
|
|
|
|
2013-01-02 08:57:39 +00:00
|
|
|
This rather intricate little dance lets us seamlessly generate correct
|
|
|
|
|
certificates even if the client has specifed only an IP address rather than the
|
|
|
|
|
hostname. It also means that we don't need to sniff additional data to generate
|
|
|
|
|
certs in transparent mode.
|
2012-04-03 23:24:58 +00:00
|
|
|
|
2013-01-02 08:57:39 +00:00
|
|
|
Upstream cert sniffing is on by default, and can optionally be turned off.
|
|
|
|
|
|
|
|
|
|
<table class="table">
|
|
|
|
|
<tbody>
|
|
|
|
|
<tr>
|
|
|
|
|
<th width="20%">command-line</th> <td>--no-upstream-cert</td>
|
|
|
|
|
</tr>
|
|
|
|
|
</tbody>
|
|
|
|
|
</table>
|
