On Mon, 05 May 2025 21:40:27 +0200,
LWS <mediomen27@gmail.com> wrote:
> 
> hi, the problem seems to be solved only on the first screen. But when you
> start using mitmproxy the logs come back in console.
> I saw that another post on the subject has passed but it seems to me that
> the py3-passlib packages have not been updated.
> I only use the system packages because I find the ports inconvenient and
> sometimes buggy. In addition to the fact that it often takes a lot of time
> to compile.

Here two things. The first one is that security/py-passlib has a maintainer:
Stuart, and I need his ok on updated. After that I'll backport it to
-stable. Anyway, here the second things: upstream introduced a regression in
passlib update: https://github.com/ThirVondukr/passlib/issues/16 and until
it's fixed I won't push an update.

But you may hack /usr/local/lib/python3.12/site-packages/passlib/registry.py
by replacing logging.debug and logging.warning into
logging.getLogger(__name__).debug and logging.getLogger(__name__).warning
see: https://marc.info/?l=openbsd-ports&m=174608694229783&w=2

> 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

-- 
wbr, Kirill