Comment # 24
on bug 9515
from Evan Huus
The only concern I can think of with that method is when doing a second pass,
the unencrypted packets (pre-starttls) might be passed to ssl incorrectly (I'm
not sure if this will happen or not, it can be checked with "tshark -2").
If this is a problem, we may need to add a 'guint32 starttls_frame' or
something to the TCP conversation data and tweak it to respect that if set.
But yes, this general approach feels cleaner to me.
You are receiving this mail because:
- You are watching all bug changes.
