You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a library (COAP.NET) that uses bouncy castle. It uses the DtlsTransport.Receive Method to handle the DTLS part everytime a package arrives.
In its current implementation it always runs the receive method in a new Task.
With this implementation Bouncy Castles DtlsRecordLayer.ProcessRecord always throws a critical error on
if (decoded.len > buffer.Length)
throw new TlsFatalAlert(AlertDescription.internal_error);
Because it tries to write larger content into a buffer sized for the previous (or maybe next) package. This only happens if the packages arrive at a somewhat fast interval and have different sizes.
User error in the COAP.NET library, or is something else going on here?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have a library (COAP.NET) that uses bouncy castle. It uses the DtlsTransport.Receive Method to handle the DTLS part everytime a package arrives.
In its current implementation it always runs the receive method in a new Task.
With this implementation Bouncy Castles DtlsRecordLayer.ProcessRecord always throws a critical error on
Because it tries to write larger content into a buffer sized for the previous (or maybe next) package. This only happens if the packages arrive at a somewhat fast interval and have different sizes.
User error in the COAP.NET library, or is something else going on here?
Beta Was this translation helpful? Give feedback.
All reactions