Changelog for 5.9.5 (v5-devel)

Friday, January 27th, 2012

Version 5.9.5 [V5-DEVEL], 2012-01-27

  • improved impstats subsystem, added many new counters
  • enhanced module loader to not rely on PATH_MAX
  • refactored imklog linux driver, now combined with BSD driver
    The Linux driver no longer supports outdated kernel symbol resolution,
    which was disabled by default for very long. Also overall cleanup,
    resulting in much smaller code. Linux and BSD are now covered by a
    single small driver.
  • $IMUXSockRateLimitInterval DEFAULT CHANGED, was 5, now 0
    The new default turns off rate limiting. This was chosen as people
    experienced problems with rate-limiting activated by default. Now it
    needs an explicit opt-in by setting this parameter.
    Thanks to Chris Gaffney for suggesting to make it opt-in; thanks to
    many unnamed others who already had complained at the time Chris made
    the suggestion ;-)

Changelog for 5.8.7 (v5-stable)

Tuesday, January 17th, 2012

Version 5.8.7  [V5-stable] 2012-01-17

  • bugfix: instabilities when using RFC5424 header fields
    Thanks to Kaiwang Chen for the patch
  • bugfix: imuxsock did truncate part of received message if it did not contain a proper date. The truncation occured because we removed that part of the messages that was expected to be the date.
    closes: http://bugzilla.adiscon.com/show_bug.cgi?id=295
  • bugfix: potential abort after reading invalid X.509 certificate
    closes: http://bugzilla.adiscon.com/show_bug.cgi?id=290
    Thanks to Tomas Heinrich for the patch
  • bugfix: stats counter were not properly initialized on creation FQDN hostname for multihomed host was not always set to the correct name if multiple aliases existed. Thanks to Tomas Heinreich for the patch.

Changelog for 6.2.0 (v6-stable)

Monday, January 9th, 2012

ChangeLog (from 6.1.12 to 6.2.0):

  • bugfix (kind of): removed numerical part from pri-text see v6 compatibility document for reasons
  • bugfix: race condition when extracting program name, APPNAME, structured data and PROCID (RFC5424 fields) could lead to invalid characters e.g. in dynamic file names or during forwarding (general malfunction of these fields in templates, mostly under heavy load)
  • bugfix: imuxsock did no longer ignore message-provided timestamp, if so configured (the *default*). Lead to no longer sub-second timestamps.
    closes: http://bugzilla.adiscon.com/show_bug.cgi?id=281
  • bugfix: omfile returns fatal error code for things that go really wrong previously, RS_RET_RESUME was returned, which lead to a loop inside the rule engine as omfile could not really recover.
  • bugfix: rsyslogd -v always said 64 atomics were not present
    thanks to mono_matsuko for the patch
  • bugfix: potential abort after reading invalid X.509 certificate closes:
    http://bugzilla.adiscon.com/show_bug.cgi?id=290
    Thanks to Tomas Heinrich for the patch
  • $Begin, $End, $StrictScoping directives have been removed as v6.4 will provide the same functionality in a far better way. So we do not want to clutter the code.

Changelog for 5.9.4 (v5-devel)

Tuesday, November 29th, 2011

Version 5.9.4 [V5-DEVEL], 2011-11-29

  • imuxsock: added capability to “annotate” messages with “trusted information”, which contains some properties obtained from the system and as such is sure to not be faked. This is inspired by the similiar idea introduced in systemd. removed dependency on gcrypt for recently-enough GnuTLS
    see: http://bugzilla.adiscon.com/show_bug.cgi?id=289
  • bugfix: imuxsock did no longer ignore message-provided timestamp, if so configured (the *default*). Lead to no longer sub-second timestamps.
    closes: http://bugzilla.adiscon.com/show_bug.cgi?id=281
  • bugfix: omfile returns fatal error code for things that go really wrong previously, RS_RET_RESUME was returned, which lead to a loop inside the rule engine as omfile could not really recover.
  • bugfix: rsyslogd -v always said 64 atomics were not present
    thanks to mono_matsuko for the patch

Changelog for 5.8.6 (v5-stable)

Friday, October 21st, 2011

Version 5.8.6  [V5-stable] 2011-10-21

  • bugfix: missing whitespace after property-based filter was not detected
  • bugfix: $OMFileFlushInterval period was doubled – now using correct value
  • bugfix: ActionQueue could malfunction due to index error
    Thanks to Vlad Grigorescu for the patch
  • bugfix: $ActionExecOnlyOnce interval did not work properly
    Thanks to Tomas Heinrich for the patch
  • bugfix: race condition when extracting program name, APPNAME, structured data and PROCID (RFC5424 fields) could lead to invalid characters e.g. in dynamic file names or during forwarding (general malfunction of these fields in templates, mostly under heavy load)
  • bugfix: imuxsock did no longer ignore message-provided timestamp, if so configured (the *default*). Lead to no longer sub-second timestamps.
    closes: http://bugzilla.adiscon.com/show_bug.cgi?id=281
  • bugfix: omfile returns fatal error code for things that go really wrong previously, RS_RET_RESUME was returned, which lead to a loop inside the rule engine as omfile could not really recover.
  • bugfix: imfile did invalid system call under some circumstances when a file that was to be monitored did not exist BUT the state file actually existed. Mostly a cosmetic issue. Root cause was incomplete error checking in stream.c; so patch may affect other code areas.
  • bugfix: rsyslogd -v always said 64 atomics were not present
    Thanks to mono_matsuko for the patch

Changelog for 6.3.6 (v6-devel)

Monday, September 19th, 2011

Version 6.3.6  [DEVEL] 2011-09-19

  • added $InputRELPServerBindRuleset directive to specify rulesets for RELP
  • bugfix: config parser did not support properties with dashes in them inside property-based filters. Thanks to Gerrit Seré for reporting this.

Changelog for 6.3.5 (v6-devel)

Thursday, September 1st, 2011

Version 6.3.5  [DEVEL] (rgerhards/al), 2011-09-01

  • bugfix/security: off-by-two bug in legacy syslog parser, CVE-2011-3200
  • bugfix: mark message processing did not work correctly
  • imudp&imtcp now report error if no listener at all was defined
    Thanks to Marcin for suggesting this error message.
  • bugfix: potential misadressing in property replacer

Changelog for 6.1.12 (v6-beta)

Thursday, September 1st, 2011

Version 6.1.12  [BETA], 2011-09-01

  • bugfix/security: off-by-two bug in legacy syslog parser, CVE-2011-3200
  • bugfix: mark message processing did not work correctly
  • bugfix: potential misadressing in property replacer
  • bugfix: memcpy overflow can occur in allowed sender checkig if a name is resolved to IPv4-mapped-on-IPv6 address
    Found by Ismail Dönmez at suse
  • bugfix: The NUL-Byte for the syslogtag was not copied in MsgDup (msg.c)
  • bugfix: fixed incorrect state handling for Discard Action (transactions)
    Note: This caused all messages in a batch to be set to COMMITTED even if they were discarded.

Changelog for 5.9.3 (v5-devel)

Thursday, September 1st, 2011

Version 5.9.3  [V5-DEVEL], 2011-09-01

  • bugfix/security: off-by-two bug in legacy syslog parser, CVE-2011-3200
  • bugfix: mark message processing did not work correctly
  • added capability to emit config error location info for warnings otherwise, omusrmsg’s warning about new config format was not accompanied by problem location.
  • bugfix: potential misadressing in property replacer
  • bugfix: MSGID corruption in RFC5424 parser under some circumstances
    closes: http://bugzilla.adiscon.com/show_bug.cgi?id=275
  • bugfix: The NUL-Byte for the syslogtag was not copied in MsgDup (msg.c)

Changelog for 4.7.5 (v4-beta)

Thursday, September 1st, 2011

Version 4.7.5  [v4-beta], 2011-09-01

  • bugfix/security: off-by-two bug in legacy syslog parser, CVE-2011-3200
  • bugfix: potential misadressing in property replacer
  • bugfix: The NUL-Byte for the syslogtag was not copied in MsgDup (msg.c)