diff options
author | Maximilian Hils <git@maximilianhils.com> | 2014-10-22 13:59:47 +0200 |
---|---|---|
committer | Maximilian Hils <git@maximilianhils.com> | 2014-10-22 13:59:47 +0200 |
commit | 3848a27d31a9b04c8114d0260c4b9a615d83c8cd (patch) | |
tree | 844e892f0d6b3eafa510560fb8e868a3571574ca /doc-src | |
parent | 6cef6fbfec92f1154b6a5b986548478137598975 (diff) | |
download | mitmproxy-3848a27d31a9b04c8114d0260c4b9a615d83c8cd.tar.gz mitmproxy-3848a27d31a9b04c8114d0260c4b9a615d83c8cd.tar.bz2 mitmproxy-3848a27d31a9b04c8114d0260c4b9a615d83c8cd.zip |
fix #378
Diffstat (limited to 'doc-src')
-rw-r--r-- | doc-src/ssl.html | 22 |
1 files changed, 19 insertions, 3 deletions
diff --git a/doc-src/ssl.html b/doc-src/ssl.html index 91225d79..16aed1dc 100644 --- a/doc-src/ssl.html +++ b/doc-src/ssl.html @@ -41,10 +41,26 @@ The files created by mitmproxy in the .mitmproxy directory are as follows: Using a custom certificate -------------------------- -You can use your own certificate by passing the __--cert__ option to mitmproxy. +You can use your own certificate by passing the <kbd>--cert</kbd> option to mitmproxy. mitmproxy then uses the provided +certificate for interception of the specified domains instead of generating a cert signed by its own CA. -The certificate file is expected to be in the PEM format. You can generate -a certificate in this format using these instructions: +The certificate file is expected to be in the PEM format. +You can include intermediary certificates right below your leaf certificate, so that you PEM file roughly looks like +this: + +<pre> +-----BEGIN PRIVATE KEY----- +<private key> +-----END PRIVATE KEY----- +-----BEGIN CERTIFICATE----- +<cert> +-----END CERTIFICATE----- +-----BEGIN CERTIFICATE----- +<intermediary cert (optional)> +-----END CERTIFICATE----- +</pre> + +For example, you can generate a certificate in this format using these instructions: <pre class="terminal"> > openssl genrsa -out cert.key 8192 |