Index | Thread | Search

From:
Kirill A. Korinsky <kirill@korins.ky>
Subject:
Re: mitmproxy and debug message in console
To:
mediomen27@gmail.com, ports@openbsd.org
Date:
Mon, 05 May 2025 22:19:03 +0200

Download raw body.

Thread
  • Kirill A. Korinsky:

    mitmproxy and debug message in console

  • On Mon, 05 May 2025 22:15:09 +0200,
    Kirill A. Korinsky <kirill@korins.ky> wrote:
    > 
    > On Mon, 05 May 2025 21:40:27 +0200,
    > LWS <mediomen27@gmail.com> wrote:
    > > Another thing I noticed is the non-functioning of the variables:
    > > 
    > > MITMPROXY_SSLKEYLOGFILE
    > > SSLKEYLOGFILE
    > > 
    > > here is some doc: https://docs.mitmproxy.org/stable/howto/wireshark-tls/
    > > these variables are used to export the encryption keys that can be used on
    > > wireshark.
    > > In the meantime instead of using mitmproxy I used mitmdump which I think
    > > should also support the variables and apparently they do not work.
    > > Thanks for everything.
    > > 
    > 
    > 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
    
    -- 
    wbr, Kirill
    
    
  • Kirill A. Korinsky:

    mitmproxy and debug message in console