harenbrs

I have the same issue, but only when I build the plugin myself from the repository. The latest packaged plugin (which is from September 2012) logs me in alright, but...

> Our core I/O happens in https://github.com/mitmproxy/mitmproxy/blob/main/mitmproxy/proxy/server.py. It probably makes sense to add it there. Alternatively we could consider a custom layer, but it's more tricky to add back pressure...

I was hoping that someone would have an answer to the original thread question (polymorphic handling of TCP and SSL streams). What is the recommended approach here?

Is this project dead? I was just about to buy but then I saw the version history. It doesn't make me feel confident that the experience is going to be...

Same thing happened to me. I don't know if those instructions are out of date or if nix needs to be set up in a particular way to run that...

I was able to do this by adding this to my `~/.config/termshark/termshark.toml`: ```toml # under [main] tshark-args = ['-o', 'ssl.keylog_file:path/to/sslkeylog.log'] ```