The overrung occurs in code for testing an interface that currently
does not exists, so the overrun can actually never happen. We fixed
it anyhow to keep Coverity scan clean of defects.
Note also that omstdout is a testbench tool not intended for
production.
Detected by Coverity scan, CID 185325
if the local hostname or IP is larger than NI_MAXHOST-1, an internal
buffer is overflowed. This is irrespective of any input data.
Detected by Coverity scan, CID 185390
- Added the 'ssl_ca' and 'ssl_cert' directives to configure ssl connexion.
- Added 'uristr' directive to configure the connexion uri directly. This directive overrides the 'uid', 'pwd', 'server' and 'serverport' directives. To create the uri, please refer to the official MongoDB Connection String documentation.
omelasticsearch made libcurl output messages to stdout. This
commit fixes that. It also automatically enables libcurl verbose
mode during debug runs - it needs to be seen if this is smart or
not (previously, code needed to be commented in).
closes https://github.com/rsyslog/rsyslog/issues/1909
When the certificate file specified in the omrelp/imrelp configuration
can't be accessed, e.g. because it doesn't exist or you don't have permission
to do so, a Segmentation Fault will appear when you start Rsyslog. This commit
fixes that problem.
closes https://github.com/rsyslog/rsyslog/issues/1869
When during a connection request the remote peer could not be
identified, imptcp could misadress memory if it is configured
to emit messages on connection open.
Detected by clang 5.0 static analyzer.
If a multi-message batch contains data errors, messages may be
duplicated as connection close is implicit commit (not rollback).
This patch introduces a specific rollback request in those cases.
closes https://github.com/rsyslog/rsyslog/issues/1829
Server-generated error messages are considered non-recoverable, while
client generated once point into connection problems (which simply can
be retried). This is part of the improvements towards better
message-induced errors. Previous commits did only handle SQL parsing
errors, now we aim to address all of the message-induced error. We assume
that all server-generated errors are such - mysql API unfortunately does
not provide a clear indication of what type if error this is and it is
out of question to check for hundereds of error codes.
closes https://github.com/rsyslog/rsyslog/issues/1830
ommysql should return RS_RET_DATAFAIL if it knows that
a message can definitely never by processed, e.g. because
of a syntax error inside the message. This helps improve
retry and suspension processing.
closes https://github.com/rsyslog/rsyslog/issues/1819
