 |
Post Aq2Pt1AJtHrPitffvc by [email protected] |
 |
More posts by [email protected] |
|
Post #Aq2Pt1AJtHrPitffvc by [email protected] |
|
0 likes, 1 repeats |
|
|
|
:mitmproxy: mitmproxy 11.1 is out! 🥳We now support *Local Capture Mode* on W… |
|
|
|
Post #Aq2Pt1LfD6w0I4yjbs by [email protected] |
|
0 likes, 1 repeats |
|
|
|
@max this sounds great, but I assume this would not work within a container/pod… |
|
|
|
Post #Aq2S46RwmfEtCpKVe4 by [email protected] |
|
0 likes, 0 repeats |
|
|
|
@thepwnicorn You'd need root, and you'd need to run mitmproxy in a netw… |
|
|
|
Post #Aq2S46ZOKzC5ZuoSFU by [email protected] |
|
0 likes, 1 repeats |
|
|
|
@max well, it has to be the current client since there seems to be something go… |
|
|
|
Post #Aq2a5iPXvh2MrbUEEa by [email protected] |
|
0 likes, 0 repeats |
|
|
|
@thepwnicorn I'm not sure I understand what you mean by "current clien… |
|
|
|
Post #Aq2a5iWdVKhzDantHk by [email protected] |
|
0 likes, 1 repeats |
|
|
|
@max right, sounded like you wanted the proxy to be TLS terminating at first. W… |
|
|
|
Post #Aq2aHKYIShqeLF7Npo by [email protected] |
|
0 likes, 1 repeats |
|
|
|
@max already went the tcpdump + Wireshark route and hence the next step with mi… |
