aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMaximilian Hils <git@maximilianhils.com>2015-03-04 23:06:58 +0100
committerMaximilian Hils <git@maximilianhils.com>2015-03-04 23:06:58 +0100
commitf45f3dd4f1e0f494c59a1af9e35a9ce38ff83ed2 (patch)
tree407f69757ecd61fd6bee0e29275090c859701445
parentff6bfba4a6a1c440018c4873d9edeb64da0f8e7f (diff)
downloadmitmproxy-f45f3dd4f1e0f494c59a1af9e35a9ce38ff83ed2.tar.gz
mitmproxy-f45f3dd4f1e0f494c59a1af9e35a9ce38ff83ed2.tar.bz2
mitmproxy-f45f3dd4f1e0f494c59a1af9e35a9ce38ff83ed2.zip
update docs
-rw-r--r--doc-src/ssl.html8
1 files changed, 6 insertions, 2 deletions
diff --git a/doc-src/ssl.html b/doc-src/ssl.html
index d8ec3d4e..de45bd29 100644
--- a/doc-src/ssl.html
+++ b/doc-src/ssl.html
@@ -72,8 +72,12 @@ For example, you can generate a certificate in this format using these instructi
Using a client side certificate
------------------------------------
-You can use a client side certificate file by specifying the directory in which the certificate is present after this argument, "--client-certs". The certificate file should be in .pem format after the url of the website whose certificate you've specified. Suppose, for example you want to open mitmproxy.com with a client side certificate, your certificate file's name should be like "mitmproxy.com.pem".
-
+You can use a client certificate by passing the <kbd>--client-certs DIRECTORY</kbd> option to mitmproxy.
+If you visit example.org, mitmproxy looks for a file named example.org.pem in the specified directory
+and uses this as the client cert. The certificate file needs to be in the PEM format and should contain
+both the unencrypted private key as well as the certificate.
+
+
Using a custom certificate authority
------------------------------------