diff options
Diffstat (limited to 'docs/src/content/concepts-certificates.md')
| -rw-r--r-- | docs/src/content/concepts-certificates.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/src/content/concepts-certificates.md b/docs/src/content/concepts-certificates.md index 20b03dc6..cf3447c7 100644 --- a/docs/src/content/concepts-certificates.md +++ b/docs/src/content/concepts-certificates.md @@ -65,7 +65,7 @@ SSL sites that your client visits. Since your browser won't trust the mitmproxy CA out of the box, you will see an SSL certificate warning every time you visit a new SSL domain through mitmproxy. When you are testing a single site through a browser, just accepting the bogus SSL cert manually is not too much trouble, but -there are a many circumstances where you will want to configure your testing +there are many circumstances where you will want to configure your testing system or browser to trust the mitmproxy CA as a signing root authority. For security reasons, the mitmproxy CA is generated uniquely on the first start and is not shared between mitmproxy installations on different devices. @@ -121,7 +121,7 @@ instructions: openssl genrsa -out cert.key 2048 # (Specify the mitm domain as Common Name, e.g. \*.google.com) openssl req -new -x509 -key cert.key -out cert.crt -cat cert.key cert.crt \> cert.pem +cat cert.key cert.crt > cert.pem {{< / highlight >}} Now, you can run mitmproxy with the generated certificate: |