diff options
author | Maximilian Hils <git@maximilianhils.com> | 2017-04-26 11:18:27 +0200 |
---|---|---|
committer | GitHub <noreply@github.com> | 2017-04-26 11:18:27 +0200 |
commit | 07cb83597b05b1355a6038d2b1ef96d7e7eb26d3 (patch) | |
tree | 0c8f21131b66f731c3eb14bbdef187844ee0e799 /docs | |
parent | e32efcae49ba5857feae85b9b4651a45d9e5fcc3 (diff) | |
download | mitmproxy-07cb83597b05b1355a6038d2b1ef96d7e7eb26d3.tar.gz mitmproxy-07cb83597b05b1355a6038d2b1ef96d7e7eb26d3.tar.bz2 mitmproxy-07cb83597b05b1355a6038d2b1ef96d7e7eb26d3.zip |
clarify that `--cert` expects a leaf certificate
refs #2254
Diffstat (limited to 'docs')
-rw-r--r-- | docs/certinstall.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/certinstall.rst b/docs/certinstall.rst index 1bd6df99..14d66d30 100644 --- a/docs/certinstall.rst +++ b/docs/certinstall.rst @@ -132,7 +132,7 @@ mitmproxy-ca-cert.cer Same file as .pem, but with an extension expected by some Using a custom certificate -------------------------- -You can use your own certificate by passing the ``--cert [domain=]path_to_certificate`` option to +You can use your own (leaf) certificate by passing the ``--cert [domain=]path_to_certificate`` option to mitmproxy. Mitmproxy then uses the provided certificate for interception of the specified domain instead of generating a certificate signed by its own CA. |