Peter M. Groen / libmodbus

It's strongly recommended to update your libmodbus library if you
use it in a slave/server application in a not trusted environment.

Debian package of libmodbus 3.0.4 already contains a patch to
mitigate the exploit but the patch isn't as strong than this one.

Thank you very much James Nutaro.

- change return argument from void to int
- update documentation

Thanks to Karl Palsson.

Thanks Tobias Doerffel.

Thanks to Carlos Tangerino

Thanks to Stefan Finzel for the bug report

Original patch for new connect function by Thomas Stalder.

- export new symbols to create specific behavior (RTU)
- the flag can't only be set by slaves
- new tests

Warning, modbus_receive returns 0 when a query is ignored.

- function removed from TCP and RTU code and from backend structure
- updated documentation
- updated examples

- new function _modbus_rtu_pre_check_confirmation
- new special test value to trigger an invalid response
- add unit test to cover invalid TID too

Thanks to Andrea Mattia

Add macros in libmodbus.txt and:
- modbus_get_byte_from_bits.txt
- modbus_get_float.txt
- modbus_reply.txt
- modbus_reply_exception.txt
- modbus_set_bits_from_byte.txt
- modbus_set_bits_from_bytes.txt
- modbus_set_float.txt

The function name was confusing because the write operation is performed
before the read. Take care to swap the arguments in the migration process.

Avoid incompatibility with GPLv2 program. This change has been approved by
Tobias Doerffel, Florian octo Forster and Hannu Vuolasaho.

The two modes are complementary, MODBUS_ERROR_RECOVERY_LINK handles
errors at data link level (bad file descriptor, timeout, etc) and
MODBUS_ERROR_RECOVERY_PROTOCOL checks Modbus error (eg. invalid
function code or trame length).

This change introduces the use of the Sleep function for Windows.
Some duplicated code has been moved from backends to modbus core.
A new debug message is now available when a flush occurs.

The unit tests are now based on this error recovery code.

The change for serial on Windows is temporary. If you're interested of
improving the situation for this, please have a look at the FIXME.

The following functions have been renamed:
- modbus_get_timeout_begin -> modbus_get_response_timeout
- modbus_set_timeout_begin -> modbus_set_response_timeout
- modbus_get_timeout_end -> modbus_get_byte_timeout
- modbus_set_timeout_end -> modbus_set_byte_timeout

The meaning of these timeout intervals is now clearer. The documentation
has been updated.

These new functions seem clearer than the recent modbus_receive_from
function IHMO. This change fixes the bandwidth-server-many-up program.

Split the original modbus_receive function in two functions to avoid
the strange -1 value to ignore the sockfd argument.

The _modbus_receive_confirmation()_ function shall receive a
request via the socket of the context 'ctx'. This function must be
used for debugging purposes because the received response isn't
checked against the initial request. This function can be
convenient to receive request not handled by the library.