This adds an alternative option to use_identity_as_username.
In contrast to use_identity_as_username this option uses the full x509 subject as the username.
The subject is formatted as an rfc4514 distingushed name e.g. CN=client,OU=unit,O=org
Signed-off-by: Fabian Ruff <fabian@progra.de>
In case that realloc fails (i.e. OOM), before exiting with "return(1)", the application is still able to free the corresponding allocated memory.
Signed-off-by: Eduardo Sanchez <ledusanchez@gmail.com>
This change in behaviour can be justified by considering when the
timeout may have occurred.
* If a connection is unreliable and has dropped, but without one end
noticing, the messages will be retried on reconnection. Sending
additional PUBLISH or PUBREL would not have changed anything.
* If a client is overloaded/unable to respond/has a slow connection then
sending additional PUBLISH or PUBREL would not help the client catch
up. Once the backlog has cleared the client will respond. If it is not
able to catch up, sending additional duplicates would not help either.
If a custom notification topic was used, the bridge status would be set
to 1 before a connection was attempted, this has been fixed.
Initial updates to the status topic are now only set once, when the
broker starts, rather than each time the bridge attempts to reconnect.
Bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=467096
Enables parallel build mode.
Accepted without CLA after discussion with Eclipse Foundation legal
about very small patches that can only be implemented in one way.
See bug report for acceptance of Certificate of Origin.
Bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=463884
Also-by: Gianfranco Costamagna <costamagnagianfranco@yahoo.it>
Inflight message count wasn't being decreased for outgoing messages using
QoS 2, meaning that only up to 20 QoS 2 messages could be sent. This has
been fixed.
Bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=464436