> > > > If you capture traffic by mitmdump or mitmproxy or mitmweb, and you had > > installed their certificate to client, it may work, see: > > https://github.com/mitmproxy/mitmproxy/blob/main/mitmproxy/net/tls.py > > > > * if libssl supports it > > Apparently it doesn't work. This is really annoying because it would be really useful to have the output traffic to be redirected to input to an IDS like suricata. I tried to export the chrome keys and I can only decrypt 30-40% of the traffic and this is quite suspicious. Thanks for everything.
- Re: mitmproxy and debug message in console Stuart Henderson
- Re: mitmproxy and debug message in console Kirill A . Korinsky
- Re: mitmproxy and debug message in console LWS
- Re: mitmproxy and debug message in consol... Theo Buehler
- Re: mitmproxy and debug message in co... LWS
- Re: mitmproxy and debug message ... Kirill A . Korinsky
- Re: mitmproxy and debug message ... Theo Buehler
- Re: mitmproxy and debug message ... LWS
- Re: mitmproxy and debug message in consol... Kirill A . Korinsky
- Re: mitmproxy and debug message in co... Kirill A . Korinsky
- Re: mitmproxy and debug message ... LWS