diff options
| author | Aldo Cortesi <aldo@nullcube.com> | 2015-05-18 12:05:29 +1200 |
|---|---|---|
| committer | Aldo Cortesi <aldo@nullcube.com> | 2015-05-18 12:05:29 +1200 |
| commit | a9f6d53562b8020b87a8feaba2ac1d16d0d869ee (patch) | |
| tree | 35ce65c646cccfdb215c22face33e3fca3763d23 /doc-src/howmitmproxy.html | |
| parent | b098556e60719bc725a3c298619f7d78f5934182 (diff) | |
| download | mitmproxy-a9f6d53562b8020b87a8feaba2ac1d16d0d869ee.tar.gz mitmproxy-a9f6d53562b8020b87a8feaba2ac1d16d0d869ee.tar.bz2 mitmproxy-a9f6d53562b8020b87a8feaba2ac1d16d0d869ee.zip | |
certificate docs: reorg, wording, tweaks
Diffstat (limited to 'doc-src/howmitmproxy.html')
| -rw-r--r-- | doc-src/howmitmproxy.html | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc-src/howmitmproxy.html b/doc-src/howmitmproxy.html index 94afd522..832a61a8 100644 --- a/doc-src/howmitmproxy.html +++ b/doc-src/howmitmproxy.html @@ -84,7 +84,7 @@ attempts to MITM an SSL connection for analysis. Our answer to this conundrum is to become a trusted Certificate Authority ourselves. Mitmproxy includes a full CA implementation that generates interception certificates on the fly. To get the client to trust these certificates, we [register mitmproxy as a trusted -CA with the device manually](@!urlTo("ssl.html")!@). +CA with the device manually](@!urlTo("certinstall.html")!@). ## Complication 1: What's the remote hostname? |