Michael Tuexen via RT wrote:
the attached patch fixes a bug where a single user message
was distributed over multiple DTLS records.
Dear Michael,
thanks for the patch. My app runs smoothly now.
I'm wondering if we can get rid of the redundant if statement that checks
if (len
Alright. Sounds good. Thanks. I checked the new version of the patch and
I do endorse it.
Just in case anybody is wondering why the patch removes the following
code segment:
/* next chunk of data should get another prepended empty fragment
* in ciphersuites with known-IV weakness: */
Hi Daniel,
the check in dtls1_write_app_data_bytes() protects against users
sending messages which are too long. An appropriate error is
signaled.
dtls1_write_bytes() is also call from DTLS internal routines
and I want to catch also error from that code path. But it might
be better not to signal
Dear all,
the attached patch fixes a bug where a single user message
was distributed over multiple DTLS records.
Best regards
Michael
fragmentation.patch
Description: Binary data
