Changelog for 5.8.5 (v5-stable)
Version 5.8.5 [V5-stable] (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
- bugfix: potential hang condition during tag emulation
- bugfix: too-early string termination during tag emulation
- 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 4.6.8 (v4-stable)
Version 4.6.8 [v4-stable] (rgerhards), 2011-09-01
- bugfix/security: off-by-two bug in legacy syslog parser, CVE-2011-3200
- bugfix: potential misadressing in property replacer
- bugfix: memcpy overflow can occur in allowed sender checking 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)
rsyslog 5.8.4 (v5-stable) released
This release contains several bugfixes for potential misadressing in the property replacer, memcpy overflow in allowed sender checking and more. For more detailed information, please read the changelog.
ChangeLog:
http://www.rsyslog.com/changelog-for-5-8-4-v5-stable/
Download:
http://www.rsyslog.com/rsyslog-5-8-4-v5-stable/
As always, feedback is appreciated.
Best regards,
Florian Riedl
rsyslog 5.8.4 (v5-stable)
Download file name: rsyslog 5.8.4 (stable)
rsyslog 5.8.4 (stable)
md5sum: a2c2a65ac84d9a895c52a754aff61986
Author: Rainer Gerhards (rgerhards@adiscon.com)
Version: 5.8.4 File size: 2.357 MB
rsyslog 6.3.4 (devel)
Download file name: rsyslog 6.3.4 (devel)
rsyslog 6.3.4 (devel)
md5sum: ff995409137125bf9fcc8b74196c35bc
Author: Rainer Gerhards (rgerhards@adiscon.com)
Version: 6.3.4 File size: 2.473 MB
rsyslog 6.3.4 (devel) released
This release brings bugfixes and further improvements to the rule engine. Most importantly, the (scoped, RainerScript-based) action object is now available. This enables users to get some early experience with the new system’s advanced features. Note that output plugins must support the new system. With this release, omfile and omusrmsg have been upgraded to support it. The next minor releases will bring more output module support for scoped actions.
Documentation for the new capabilities is upcoming at http://www.rsyslog.com/doc/node1.html
ChangeLog:
http://www.rsyslog.com/changelog-for-6-3-4-v6-devel/
Download:
http://www.rsyslog.com/rsyslog-6-3-4-devel/
As always, feedback is appreciated.
Best regards,
Florian Riedl
Changelog for 6.3.4 (v6-devel)
Version 6.3.4 [DEVEL] (rgerhards), 2011-08-02
- added support for action() config object
- in rsyslog core engine
- in omfile
- in omusrmsg
- bugfix: omusrmsg format usr1,usr2 was no longer supported
- bugfix: misaddressing in config handler. In theory, can cause segfault, in practice this is extremely unlikely. Thanks to Marcin for alertig me.
rsyslog 6.3.3 config format improvements
In rsyslog 6.3.3, the config processor has finally changed. The old legacy processor (and with it the early RainerScript implementation) is thrown out and has been replaced by the so-called RainerScript processor (why that crazy name?). This is an extremely important step for rsyslog, as it now has the foundation for a much better and intuitive rsyslog.conf format. However, most of that can not be seen in 6.3.3, as it requires more work, especially in the plugin arena. Still, there are a couple of smaller improvements available.
Most importantly, the performance of script based filters has been considerably enhanced. Preliminary testing shows a three times speedup (we’ll do more benchmarking at a later stage; there is also still lots of room for optimization ;-)).
The ugliness of continuation lines has been removed. They may still be used, and this may make a lot of sense with some actions, but you are usually no longer forced to use continuation lines. Take this config snippet from a leading distro:
if ( \ /* kernel up to warning except of firewall */ \ ($syslogfacility-text == 'kern') and \ ($syslogseverity <= 4 /* warning */ ) and not \ ($msg contains 'IN=' and $msg contains 'OUT=') \ ) or ( \ /* up to errors except of facility authpriv */ \ ($syslogseverity <= 3 /* errors */ ) and not \ ($syslogfacility-text == 'authpriv') \ ) \ then /dev/tty10 & |/dev/xconsole
This can now be written as follows:
if ( /* kernel up to warning except of firewall */ ($syslogfacility-text == 'kern') and ($syslogseverity <= 4 /* warning */ ) and not ($msg contains 'IN=' and $msg contains 'OUT=') ) or ( /* up to errors except of facility authpriv */ ($syslogseverity <= 3 /* errors */ ) and not ($syslogfacility-text == 'authpriv') ) then /dev/tty10 & |/dev/xconsole
rsyslog 5.9.1 (devel)
Download file name: rsyslog 5.9.1 (devel)
rsyslog 5.9.1 (devel)
md5sum: 99b0f1b9e16f664512ae2f7467eb5c59
Author: Rainer Gerhards (rgerhards@adiscon.com)
Version: 5.9.1 File size: 2.3 MB
rsyslog 4.6.6 (v4-stable) released
We have just released rsyslog 4.6.6, the new v4-stable.
This is a maintenance release for the current v4-stable branch. It contains some important bug fixes. It is highly recommended to upgrade to this version.
Please see the ChangeLog for more details.
ChangeLog:
http://www.rsyslog.com/changelog-for-4-6-6-v4-stable/
Download:
http://www.rsyslog.com/rsyslog-4-6-6-v4-stable/
As always, feedback is appreciated.
Best regards,
Tom Bergfeld
