1. Allow the MTU size to be changed at compile time for memory
contrained environments using static memory.
2. Add compile time option to disable the check for DTLS messages
in the current epoch with an outside-the-window sequence number.
wolfSSL_set_secret() was checking the preMasterSz against the sizeof
the preMasterSecret member of the Arrays structure. That member
was changed to a pointer and allocated dynamically for the session
write-duping. The comparison between the passed in size and the size
of the parameter started failing. The check now uses the constant
that is used for allocating the preMasterSecret member.
other options.
1. Missing prototype for the Mcast receive I/O callback.
2. When disabling SHA-1, the old DTLS cookie callback wouldn't work.
Allow for SHA-256.
1. Used quotes rather than angle-brackets when including
user_settings.h.
2. Used angle-brackets rather than quotes when including
the ThreadX and NetX headers.
3. Added a define flag to include types.h with NetX or ThreadX.
4. Added a void typecast to hush a warning about an unused variable
in the I/O callbacks for NetX.
5. Clean up static analysis warning in the peer sequence
number selection for DTLS.
1. Restore original EmbedRecvFrom callback.
2. Add new EmbedRecvFromMcast callback. (EmbedSendTo still the same.)
3. Set new receive from callback when setting the member ID.
4. Fixed bad rebase change.
1. Adding the prototypes for the sequence number high water callback.
2. Added the accessors to set the highwater callback function,
trigger levels, and application context.
3. Calls the highwater callback at specified sequence number thresholds
per peer.
1. Separated the peer ID from the array index into the peer sequence
list. This allows peer IDs to range from 0..255, and to have an
arbitrary size for the sequence list.
2. Add API to add and remove peer IDs from the sequence number list.
1. Temporary change to io.c to recieve datagrams from any peer.
2. Uses an array of Peer Sequence structures to track the current
sequence number of all the peers.
1. When setting the key data, use same keys for server and client
sides of the different keys. This feels a little kludgey, and
won't work when using separate senders and listeners who may
use unicast messages. But this works for the all peers are
multicast senders case.
