Changelog for 8.2.2 (v8-stable)

Version 8.2.2 [v8-stable] 2014-06-02

  • made the missing (contributed) modules build under v8
    Note that we could do this to the stable, because there is NO regression chance at all: only the modules themselves were changed, and they did NOT work at all previously. Please also note that most of these modules did not yet receive real testing. As we don’t have the necessary environments (easily enough available), we depend on users submitting error reports and helping to iron out any issues that may arise.
    Modules:

    • mmrfc5424addhmac
    • omrabbitmq
    • omgssapi
    • omhdfs
    • omzmq3

rsyslog 8.3.2 (v8-devel) released

We have just released 8.3.2 of the v8-devel branch.

This is primarily a bug-fixing release, but it also adds the ability to extract parts of a timestamp via the property replacer and adds support for per-listener imrelp rulesets (thanks to bobthesecurityguy for the patch!).

ChangeLog:

http://www.rsyslog.com/changelog-for-8-3-2-v8-devel/

Download:

http://www.rsyslog.com/download-v8-devel/

As always, feedback is appreciated.

Best regards,
Florian Riedl

librelp 1.2.7

librelp 1.2.7 [download]

This is a bugfixing release of librelp. It fixes incompatabilities with C++ and some bugs with wildcards.

———————————————————————-
Version 1.2.7 – 2014-04-29
– bugfix: librelp was incompatible with C++ without a real reason
  Thanks to Ivan Kryak for the patch
– bugfix: potential misadressing in wildcard match
  see: https://github.com/rsyslog/librelp/pull/3
  Thanks to Sebastian Schmidt for the patch.
– bugfix: always last wildcard match was reported, not first
  see: https://github.com/rsyslog/librelp/pull/4
  Thanks to Sebastian Schmidt for the patch.


sha256sum: 3a434a1c71772706104cfb1c93ba8e6809d257851d60de29ac2142c60c68d7d1

rsyslog 8.3.1 (v8-devel) released

We have just released 8.3.1 of the v8-devel branch.

This release provides some improvements for external message modification modules, a module to rewrite message facility and severity as well as bug fixes. It is a recommended update for all v8.3 users.

ChangeLog:

http://www.rsyslog.com/changelog-for-8-3-1-v8-devel/

Download:

http://www.rsyslog.com/download-v8-devel/

As always, feedback is appreciated.

Best regards,
Florian Riedl

Changelog for 8.3.1 (v8-devel)

Version 8.3.1 [v8-devel] 2014-04-24

  • external message modification interface now support modifying message PRI
  • “jsonmesg” property will include uuid only if one was previously generated
    This is primarily a performance optimization. Whenever the message uuid is gotten, it is generated when not already present. As we used the regular setter, this means that always the uuid was generated, which is quite time-consuming. This has now been changed so that it only is generated if it already exists. That also matches more closly the semantics, as “jsonmesg” should not make modifications to the message.
    Note that the same applies to “fulljson” passing mode for external plugins.
  • added plugin to rewrite message facility and/or severity
    Name: fac-sever-rewrite.py
  • permits to build against json-c 0.12
    Unfortunately, json-c had an ABI breakage, so this is necessary. Note that versions prior to 0.12 had security issues (CVE-2013-6370, CVE-2013-6371) and so it is desirable to link against the new version.
    Thanks to Thomas D. for the patch.
    Note that at least some distros have fixed the security issue in older versions of json-c, so this seems to apply mostly when building from sources.
  • bugfix: using UUID property could cause segfault
  • bugfix/mmexternal: memory leak
  • bugfix: memory leak when using “jsonmesg” property
  • bugfix: mmutf8fix did not detect two invalid sequences
    Thanks to Axel Rau for the patch.
  • bugfix: build problems with lexer.l on some platforms
    For some reason, the strdup() prototype and others are missing. I admit that I don’t know why, as this happens only in 8.3.0+ and there is no indication of changes to the affected files. In any case, we need to fix this, and the current solution works at least as an interim one.

rsyslog 8.2.1 (v8-stable) released

We have just released 8.2.1 of the v8-stable branch.

This release permits to build against json-c 0.12. Due to the ABI breckage, this is necessary. Json-c versions prior to 0.12 had security issues, so this is desirable. At least some distros have fixed the security issue in older versions of json-c, so this seems to apply mostly when building from sources.

Additionaly, the doc is no longer shipped as part of the rsyslog tarball to allow de-coupled release cycles.

Download: http://www.rsyslog.com/downloads/download-v8-stable/

As always, feedback is appreciated.

Best regards,
Florian Riedl

Changelog for 8.2.1 (v8-stable)

Version 8.2.1 [v8-stable] 2014-04-17

  • permits to build against json-c 0.12
    Unfortunately, json-c had an ABI breakage, so this is necessary. Note that versions prior to 0.12 had security issues (CVE-2013-6370, CVE-2013-6371) and so it is desirable to link against the new version.
    Thanks to Thomas D. for the patch. Note that at least some distros have fixed the security issue in older versions of json-c, so this seems to apply mostly when building from sources.
  • doc is no longer shipped as part of the rsyslog tarball
    Instead, the rsyslog-doc project creates its own tarball. This is the result of a mailing list discussion after the 8.2.0 release with a tarball-in-tarball approach, which was disliked by almost all distro maintainers. This move also has the advantage of de-coupling the release cycles of both projects a bit (which turned out to be a bit problematic in practice).
  • bugfix: mmutf8fix did not detect two invalid sequences
    Thanks to Axel Rau for the patch.

RSyslog Windows Agent 2.2 Released

Adiscon is proud to announce the 2.2 release of RSyslog Windows Agent.

This is the maintenance release and contains mainly bugfixes.

Most notably, this version includes OpenSSL library 1.0.1g. This fixes the latest openssl security issues known as heartbleed.

Remote Eventlog Monitoring in Eventlog Monitor V2 has been improved.

Detailed information can be found in the version history below.

Build-IDs: Service 2.2.117, Client 2.2.0.141

Features

  • Updated embedded OpenSSL library to 1.0.1g

Bugfixes

  • EventLog Monitor V2: Fixed a problem reading the “Process unknown/unconfigured Eventlog Channgels” option which was added in the last minor update.
  • EventLog Monitor V2: Fixed a problem when using “Remote EventLog Monitoring”. Now logsources are read from the remote machine properly.
  • Engine: Fixed startup issues reading windows registry. This problem only applied if you configured the service to run with an user account that has insufficient write rights into the windows registry.

 

Version 2.2 is a free download. Customers with existing 1.x keys can contact our Sales department for upgrade prices. If you have a valid Upgrade Insurance ID, you can request a free new key by sending your Upgrade Insurance ID to sales@adiscon.com. Please note that the download enables the free 30-day trial version if used without a key – so you can right now go ahead and evaluate it.

rsyslog 8.3.0 (v8-devel) released

We have just released 8.3.0 of the v8-devel branch.

This opens the next iteration of the v8-devel branch. As its most important feature, this release offers the external plugin message modification interface and comes with a full sample of a credit card anonymizer in python.

ChangeLog:

http://www.rsyslog.com/changelog-for-8-3-0-v8-devel/

Download:

http://www.rsyslog.com/download-v8-devel/

Feedback is *very much* appreciated.

Best regards,
Florian Riedl

Changelog for 8.3.0 (v8-devel)

Version 8.3.0 [v8-devel] 2014-04-10

  • new plugin for anonymizing credit card numbers
    Thanks to Peter Slavov for providing the code.
  • external message modification modules are now supported
    They are bound via the new native module “mmexternal”. Also, a sample skeleton for an external python message modification module has been added.
  • new $jsonmesg property with JSON representation of whole message object
    closes: https://github.com/rsyslog/rsyslog/issues/19
  • improved error message for invalid field extraction in string template
    see also:
    http://kb.monitorware.com/problem-with-field-based-extraction-t12299.html
  • fix build problems on Solaris
  • NOTE: a json-c API that we begun to use requires the compiler to be in c99 mode. By default, we select it automatically. If you modify this and use gcc, be sure to include “-std=c99” in your compiler flags. This seems to be necessary only for older versions of gcc.
Scroll to top