Grasscutters/mitmproxy
3
0
Fork 0
mirror of https://github.com/Grasscutters/mitmproxy.git synced 2024-11-25 09:37:37 +00:00
Code Issues Projects Releases Wiki Activity

docs: requirements for custom mitmproxy-ca.pem (#4601)

Browse Source 
* docs: requirements for custom mitmproxy-ca.pem

* docs: fix typos
This commit is contained in:
Zoltán Reegn 2021-05-24 12:19:45 +02:00 committed by GitHub
parent 8af4055e3b
commit 01c18c109b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 21 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
docs/src/content/concepts-certificates.md
View File

@ -151,6 +151,27 @@ mitmproxy. Mitmproxy will then look for `mitmproxy-ca.pem` in the
specified directory. If no such file exists, it will be generated
automatically.
The `mitmproxy-ca.pem` certificate file has to look roughly like this:
-----BEGIN PRIVATE KEY-----
<private key>
-----END PRIVATE KEY-----
-----BEGIN CERTIFICATE-----
<cert>
-----END CERTIFICATE-----
When looking at the certificate with
`openssl x509 -noout -text -in ~/.mitmproxy/mitmproxy-ca.pem`
it should have at least the following X509v3 extensions so mitmproxy can
use it to generate certificates:
X509v3 extensions:
X509v3 Key Usage: critical
Certificate Sign
X509v3 Basic Constraints: critical
CA:TRUE
## Using a client side certificate
You can use a client certificate by passing the `--set client_certs=DIRECTORY|FILE`