IETF QUIC TLS decryption errors when packets are coalesced with random data
Wireshark gets confused when IETF QUIC packets are coalesced with random data (which is legal), and stops decrypting further valid packets in either direction.
Steps to reproduce
The quant runs in https://interop.seemann.io/ can be configured to reproduce this. (Note that I have turned off this padding with random at the moment, to avoid triggering the bug.)
What is the current bug behavior?
TLS decryption of the QUIC stream fails.
What is the expected correct behavior?
TLS decryption of the QUIC stream should continue.