Bug 1916558 Comment 11 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
(In reply to Kagami Rosylight [:saschanaz] (they/them) from comment #8)
> > LogMessages — (neqo_transport::*) [neqo_transport] Crypto operation failed NssError { name: "SEC_ERROR_BAD_DATA", code: -8190, desc: "security library: received bad data." }
> > LogMessages — (neqo_transport::*) [neqo_transport::stats] [Client ...] Dropped received packet: Decryption failure; Total: 27
> 
> This constantly happens, interesting.

This is a red herring - this is the message that gets printed when QUIC packets are padded with garbage. We should probably lower the log level of that message, or only log it if it is not a coalesced garbage packet that triggers it.
Revision 1 by
on 
(In reply to Kagami Rosylight [:saschanaz] (they/them) from comment #8)
> > LogMessages — (neqo_transport::*) [neqo_transport] Crypto operation failed NssError { name: "SEC_ERROR_BAD_DATA", code: -8190, desc: "security library: received bad data." }
> > LogMessages — (neqo_transport::*) [neqo_transport::stats] [Client ...] Dropped received packet: Decryption failure; Total: 27
> 
> This constantly happens, interesting.

This is a red herring - this is the message that gets printed when QUIC packets are padded with garbage. We should probably lower the log level of that message, or only log it if it is not a coalesced garbage packet that triggers it.

Edit: But there sure are more of those than there should be...
Revision 2 by
on 
(In reply to Kagami Rosylight [:saschanaz] (they/them) from comment #8)
> > LogMessages — (neqo_transport::*) [neqo_transport] Crypto operation failed NssError { name: "SEC_ERROR_BAD_DATA", code: -8190, desc: "security library: received bad data." }
> > LogMessages — (neqo_transport::*) [neqo_transport::stats] [Client ...] Dropped received packet: Decryption failure; Total: 27
> 
> This constantly happens, interesting.

This is possibly a red herring - this is the message that gets printed when QUIC packets are padded with garbage. We should probably lower the log level of that message, or only log it if it is not a coalesced garbage packet that triggers it.

Edit: But there sure are more of those than there should be...

Back to Bug 1916558 Comment 11