------------------------------------------------------------------------------ PACKAGE : syslog-ng Premium Edition VERSION : 3.0.6 SUMMARY : new stable release DATE : Jul 21, 2010 ------------------------------------------------------------------------------ DESCRIPTION: A new stable version of syslog-ng Premium Edition (3.0.6) has been released. For latest fixes in the 3.0.x branch you are recommended to upgrade to this version. CHANGES: 3.0.6 Tue, 20 Jul 2010 16:14:17 +0100 General * The lgstool utility reported "record too large" errors on some logstore files. This has been a problem in the lgstool utility, not in the logstore files themselves. This has been corrected. * The syslog-ng PE application now ensures that the last chunks of logstore files are properly timestamped even if syslog-ng is terminated. * Non-file (for example pipe or tcp) destinations with flush_timeout() set to non-zero may cause high CPU usage as long as the destination is stalled. The situation resolved itself when the destination became writable again. This has been corrected. * Fixed a possible but rare memory leak in the handling of message suppression. * The default configuration file was incorrectly using the program_override() option, causing an extra ':' to be added to kernel log messages. This has been corrected. * Corrections in the handling of octal and hexadecimal numbers literals. * The syslog-ng application automatically stays in the foreground when performing configuration syntax checks (--syntax-only) or when started in debug mode (-d). * The syslog-ng PE application now ensures that numbers are never resolved using getpwnam/getgrnam functions, because this may cause deadlocks if the NSS provider is LDAP and the LDAP server is trying to log a message to syslog about invalid usernames. * When several SIGHUP signals are received in quick succession, the last one may have been dropped. This problem is fixed. * When syslog-ng is reloaded, the local hostname value was not refreshed, causing syslog-ng to remember the hostname until the next restart. This may not play nice with DHCP configured hostnames, which may change dynamically. * Fixed a boundary checking error on the usertty() destination, which can cause a local buffer to be overflown if the wtmp file on the system contains more than 123 characters in its ut_line member. It is not believed to be exploitable on the following platforms: Linux (32 chars) Solaris (12 chars) AIX (64 chars) HP-UX (12 chars) FreeBSD (8 chars) OpenBSD (8 chars) * Using the greedy and drop-invalid flags of the csv-parser() together caused syslog-ng to reject messages. This has been corrected. * So far, opening a file with the pipe() source driver (or a pipe with the file() driver) has been considered as an error. From now on, syslog-ng gives only a warning about such situations. * The dir_perm, dir_user and dir_group options were not available for logstore destinations. This has been corrected. * It was not possible to leave the ownership, permission, and group settings of existing log files and directories unchanged, because the owner(-1) setting always inherited the global settings. Now using these attributes without specifying an argument (for example, 'owner()') leaves the properties of the file unchanged. * When using templates to format messages, it is now possible to use the dollar-sign ($) in a template literally. Including two dollar signs in the template will result in a single dollar sign in the messages. * The syslog-ng.8 and syslog-ng.conf.5 man pages have been updated, and a new man page has been added for the loggen tool. Solaris * The Solaris 10 SMF script now checks if the pid file refers to an actual instance of syslog-ng to make sure that syslog-ng is started even after a system crash. * Corrections to the Solaris init scripts. AIX * The syslog-ng application did not automatically start on IBM AIX systems after the system was rebooted. This has been corrected. Debian, RPM installer * RPM and DEB packages now can rotate the /var/log/messages file, using a newly added logrotate script: /etc/logrotate.d/opt-syslog-ng DOWNLOAD: Download the latest binaries from: http://www.balabit.com/network-security/syslog-ng/central-syslog-server/upgr... Note that to download the binaries, you have to login into your MyBalaBit account. The documentation of the syslog-ng application is available in The syslog-ng 3.0 Administrator Guide at: http://www.balabit.com/support/documentation/?product=syslog-ng&type=all&language[en]=en&