V2.3.3 Patch 1

Updated FreeRTOS_inet_pton4() so it rejects IP addresses that
have leading zeros. Previously, if the IP address had leading
zeros, perhaps because it was entered in octal format, the
address was interpreted as decimal (the leading zeros were
stripped). That could result in the function returning an
unexpected IP address.

V2.3.4

FreeRTOS+TCP only. Version 2.3.4.

Changes between V2.3.3 and V2.3.4 releases:
+ Added a check in BufferAllocation_2.c to ensure adding (2 +
ipBUFFER_PADDING) bytes to the requested allocation size does
not cause an integer overflow. Thanks to Bernard Lebel
(RMDS Innovation) reporting this potential issue.
+ Updated FreeRTOS_inet_pton4() so it rejects IP addresses that
have leading zeros. Previously, if the IP address had leading
zeros, perhaps because it was entered in octal format, the
address was interpreted as decimal (the leading zeros were
stripped). That could result in the function returning an
unexpected IP address.
+ Added logic to clear flags of a stored TCP packet to avoid
sending incorrect flags when receiving incorrect packets from
the peer.
+ Fixed the IP header checksum calculation of ICMP response.

V2.3.2 LTS Patch 1

Changes between V2.3.2 and V2.3.2 LTS Patch 1

+ In BufferAllocation_2.c
   (https://github.com/FreeRTOS/FreeRTOS-Plus-TCP/blob/main/portable/BufferManagement/BufferAllocation_2.c),
   there is an unchecked possible addition overflow when calculating the size of the block
   of memory to be allocated for a network buffer that could result in the size overflowing
   and the allocation returning success but allocating only a fraction of the memory asked 
   for. With default settings, this would only occur when attempting to allocate within
   12 bytes of 4 GB. Thanks to Bernard Lebel (RMDS Innovation) for reporting this potential
   issue.
+ Update FreeRTOS_inet_pton4() so it rejects IP addresses that have leading zeros.
   Previously, if the IP address had leading zeros, perhaps because it was entered in octal
   format, the address was interpreted as decimal (the leading zeros were stripped). That
   could result in the function returning an unexpected IP address, and so also to unwanted
   behavior.

V2.3.3

Update History.txt to reflect the latest changes. (#267)

* Update history.txt

* Remove trailing whitespace

* Update the wording in the history file.

V2.3.2

Update Kernel Submodule pointer and the README for release (#126)

* Update for release

* Minor update

* Update Kernel submodule

* Minor correction

V2.3.1

Update version number and history (#61)

* Update the version numbers

* Update History.txt file

* Correction after @gitwallit's comments

V2.3.0

Create pull_request_template.md

V2.2.2

TCP: Update version number and History.txt (#247)

* Update the version number
* Update History.txt