Replies: 1 comment 1 reply
-
https://docs.mitmproxy.org/stable/concepts-certificates/ has some instructions on certificate generations. Additions/updates are welcome! For your particular use case, you can maybe also just delete your |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have an IoT device and by firmware analysis I seem to have stumbled upon a "feature" that lets it skip cert verification if the cert is expired (it just ignores the cert then and allows traffic, also mentioning this in the logs).
Namely, it normally checks for
/CN=<important-to-get-right>/
.My IoT device is using a different firmware revision (undumped) so I'm not sure if this "feature" works on my device.
However, I don't know how to work with certificates (meaning I don't know how to generate such a CA cert) and I'd prefer if mitmproxy gave me the option to provide an expired certificate.
I'd be grateful if someone could show me how to generate a new mitmproxy CA cert with a specified date range.
Ideally this would already be a feature of mitmweb (more control over CA cert).
Beta Was this translation helpful? Give feedback.
All reactions