From a9f6d53562b8020b87a8feaba2ac1d16d0d869ee Mon Sep 17 00:00:00 2001 From: Aldo Cortesi Date: Mon, 18 May 2015 12:05:29 +1200 Subject: certificate docs: reorg, wording, tweaks --- doc-src/howmitmproxy.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc-src/howmitmproxy.html') 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? -- cgit v1.2.3