docs: how to create the proper CA (#5370)

Co-authored-by: Maximilian Hils <git@maximilianhils.com>
This commit is contained in:
Alessandro Surace 2024-03-11 11:10:06 +01:00 committed by GitHub
parent a8603cac0d
commit 1a489f6a8c
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 8 additions and 0 deletions

View File

@ -9,6 +9,8 @@
* Fix multipart form content view being unusable.
([#6653](https://github.com/mitmproxy/mitmproxy/pull/6653), @DaniElectra)
* Documentation Improvements on CA Certificate Generation
([#5370](https://github.com/mitmproxy/mitmproxy/pull/5370), @zioalex)
## 07 March 2024: mitmproxy 10.2.4

View File

@ -191,6 +191,12 @@ use it to generate certificates:
X509v3 Basic Constraints: critical
CA:TRUE
For example, when using OpenSSL, you can create a CA authority as follows:
```shell
openssl req -x509 -new -nodes -key ca.key -sha256 -out ca.crt -addext keyUsage=critical,keyCertSign
cat ca.key ca.crt > mitmproxy-ca.pem
```
## Using a client side certificate