Capability to Add Advanced Filters Similar to ignore_hosts in MITMProxy

[SeshaPhaniVV]

Hi Team,

First and foremost, thank you for developing and maintaining such an outstanding tool in MITMProxy.

I have a question regarding the implementation of advanced filtering mechanisms. For example, I am looking to add filters based on payload attributes such as size, headers etc., while maintaining TLS encryption integrity.

For instance, I would like to implement a filter that intercepts traffic if the payload size exceeds 10KB, and allows smaller payloads to pass through without interception.

Is there a way to achieve this within the current architecture of MITMProxy? If so, could you please provide guidance or reference materials on how to implement these filters without compromising the TLS encryption?

Thank you in advance for your assistance!

[mhils]

This is generally not possible due to the design of TLS. Headers and payload size are not yet known when the decision to intercept needs to be made. The client will only transmit this information once the handshake is complete.

…

On Tue, May 14, 2024, 03:08 SeshaPhaniVV ***@***.***> wrote: Hi Team, First and foremost, thank you for developing and maintaining such an outstanding tool in MITMProxy. I have a question regarding the implementation of advanced filtering mechanisms. For example, I am looking to add filters based on payload attributes such as size, headers etc., while maintaining TLS encryption integrity. For instance, I would like to implement a filter that intercepts traffic if the payload size exceeds 10KB, and allows smaller payloads to pass through without interception. Is there a way to achieve this within the current architecture of MITMProxy? If so, could you please provide guidance or reference materials on how to implement these filters without compromising the TLS encryption? Thank you in advance for your assistance! — Reply to this email directly, view it on GitHub <#6848>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHY2PU2X3DSSVLOBSJNP5LZCFPY5AVCNFSM6AAAAABHVGFP3SVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZWGY3DGNZUGQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>