August 2010 - syslog-ng-announce

syslog-ng Agent for Windows 3.0.8 has been released
by devel＠balabit.hu 05 Aug '10

05 Aug '10

------------------------------------------------------------------------------ PACKAGE : syslog-ng Agent for Windows VERSION : 3.0.8 SUMMARY : new stable release DATE : Aug 4, 2010 ------------------------------------------------------------------------------ DESCRIPTION: A new stable version of syslog-ng Agent for Windows (3.0.8) has been released. For latest fixes in the 3.0.x branch you are recommended to upgrade to this version. CHANGES: 3.0.8 Wed, 4 Aug 2010 10:20:55 +0100 Core: * When the syslog-ng Agent had 62 or more sources, sometimes it resulted in 100% of CPU usage. This has been corrected. * Changed the facility names "auth" (code 10) to "authpriv", and "cron" (code 15) to "solaris-cron" in the syslog-ng Agent GUI. File Sources: * When reading from wildcarded file source, syslog-ng Agent will now recognize renamed files. * When reading from a file source, syslog-ng Agent mishandled lines with more than 8192 characters. These were split into two separate log entries. This has been corrected. * syslog-ng Agent inserted an extra CR (ASCII 13) character at the end of the FILE_MESSAGE macro, causing problems when this macro was not the last one in the template. This behaviour has been corrected. HOW TO UPGRADE * When upgrading a machine running version 3.0.3 or later in standalone mode, run the .exe installer and verify that the displayed information is correct. * When upgrading a machine running version 3.0.3 or later in domain mode, follow the steps described in section 'Installing the syslog-ng Agent on the hosts of a domain' of the documentation. The system will automatically recognize that the new package will update the syslog-ng Agent for Windows package. DOWNLOAD: Download the latest binaries from: http://www.balabit.com/network-security/syslog-ng/central-syslog-server/upg… Note that to download the binaries, you have to login into your MyBalaBit account. The documentation of the syslog-ng Agent for Windows application is available in The syslog-ng 3.0 Administrator Guide at: http://www.balabit.com/support/documentation/?product=syslog-ng&type=all&la…

1 0

syslog-ng Agent for Windows 3.1.1 has been released
by devel＠balabit.hu 05 Aug '10

05 Aug '10

------------------------------------------------------------------------------ PACKAGE : syslog-ng Agent for Windows VERSION : 3.1.1 SUMMARY : new feature release DATE : Aug 4, 2010 ------------------------------------------------------------------------------ DESCRIPTION: A new feature version of syslog-ng Agent for Windows (3.1.1) has been released. For latest fixes in the 3.1.x branch you are recommended to upgrade to this version. CHANGES: 3.1.1 Wed, 4 Aug 2010 10:20:55 +0100 BUGFIXES Core: * When the syslog-ng Agent had 62 or more sources, sometimes it resulted in 100% of CPU usage. This has been corrected. * There was a possible situation when syslog-ng Agent crashed in debug mode. This has been corrected. * Changed the facility names "auth" (code 10) to "authpriv", and "cron" (code 15) to "solaris-cron" in the syslog-ng Agent GUI. Eventlog Sources: * When the event message format is configured to SNARE Compatible Message Type, and the event (in $EVENT_MSG or $EVENT_MESSAGE macros) contains tab character or carriage return, line feed characters, syslog-ng Agent will replace them with space (in case of tab) and double space (in case of carriage return, line feed) in the outgoing message. File Sources: * When reading from wildcarded file source, syslog-ng Agent will now recognize renamed files. * When reading from a file source, syslog-ng Agent mishandled lines with more than 8192 characters. These were split into two separate log entries. This has been corrected. * syslog-ng Agent inserted an extra CR (ASCII 13) character at the end of the FILE_MESSAGE macro, causing problems when this macro was not the last one in the template. This behaviour has been corrected. Miscellaneous changes: * Added dbghelp.dll file to the installer, for creating crash dumps. * Corrected the descriptions of syslog-ng-agent-conf.xsd file. HOW TO UPGRADE WARNING Upgrading to syslog-ng Agent version 3.1 is supported only from syslog-ng Agent version 3.0.7. WARNING Downgrading from a feature release to an earlier (and thus unsupported) feature release, or to the stable release is not supported: this means that once you upgrade a system from a stable release (e.g., 2.0) to a feature release (e.g., 2.1), you will have to keep upgrading to the new feature releases until the next stable version release (e.g., 3.0) is published, or risk using an unsupported product. Both the stable and the feature branches will be supported via maintenance (e.g., bugfix) releases. * When upgrading a machine running version 3.0.7 in standalone mode, run the .exe installer and verify that the displayed information is correct. * When upgrading a machine running version 3.0.7 in domain mode, follow the steps described in section 'Installing the syslog-ng Agent on the hosts of a domain' of the documentation. The system will automatically recognize that the new package will update the syslog-ng Agent for Windows package. DOWNLOAD: Download the latest binaries from: http://www.balabit.com/network-security/syslog-ng/central-syslog-server/upg… Note that to download the binaries, you have to login into your MyBalaBit account. The documentation of the syslog-ng Agent for Windows application is available in The syslog-ng Agent for Windows 3.1 Administrator Guide at: http://www.balabit.com/support/documentation/?product=syslog-ng&type=all&la…

1 0

syslog-ng 3.1.2 has been released
by devel＠balabit.hu 04 Aug '10

04 Aug '10

------------------------------------------------------------------------------ PACKAGE : syslog-ng VERSION : 3.1.2 SUMMARY : new stable release DATE : Aug 4, 2010 ------------------------------------------------------------------------------ DESCRIPTION: A new stable version of syslog-ng Open Source Edition (3.1.2) has been released. For latest fixes in the 3.1.x feature branch you are recommended to upgrade to this version. CHANGES: 3.1.2 Mon, 02 Aug 2010 17:06:28 +0200 INCOMPATIBLE CHANGES: * This release changes the default for 'store-legacy-msghdr' flag for log sources. In previous releases this had to be enabled explicitly, because of the performance penalties, which do not apply to 3.1. The original behaviour can be restored by explicitly specifying 'dont-store-legacy-msghdr'. See this blog post for more details: http://bazsi.blogs.balabit.com/2010/05/small-incompatible-change-for-31.html Bugfixes: * 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. * When several SIGHUP signals are received in quick succession, the last one may have been dropped. This problem is fixed. * Make sure that numbers never get resolved using getpwnam/getgrnam (e.g. libnss 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. * Fixed flush_timeout() handling in for non-file destinations. Enabling flush_lines()/flush_timeout() for a non-file destination, either using a global option, or a per-destination option could cause excess CPU usage as long as the destination wasn't writable. * In case patterndb has a syntax error when reloading the file, syslog-ng automatically reverts to the old version instead of dropping pattern matching altogether. * Fixed pdbtool to properly handle accented characters in the command line. * Fixed the use of the greedy and drop-invalid flags for csv-parser. * Fixed a possible but rare memory leak in the handling of message suppression. Other changes: * Added "update-patterndb" command that merges patterndb files from ${sysconfdir}/patterndb.d and produces ${localstatedir}/patterndb.xml, the default file of the db-parser(). * Make it possible to specify the path to the syslog-ng control socket using a command line option in order to make it easier to launch multiple syslog-ng instances. * Introduced a new, cleaner syntax to specify that the permissions of a file are not to be changed. Use owner/group/perm options of a file without any parameters instead of "-1". The old mechanism had the problem that both per-file and global settings had to use "-1" to effectively stop syslog-ng from changing the uid/gid/perm values. The new syntax will make it possible to specify defaults in the global options section and customize those on a per-file basis. * syslog-ng will not go into the background if either the --syntax-only or --debug options are specified. Loggen: * Added SSL support. * Added the ability to read from a sample file Credits: * We would like to send our thank for all contributors sending us bugreports, documentation issues or patches. They are: * Marius Tomaschewski * Corey Hickey * Evan Rempel * Andy Kitchingman * andrewn at locus.net Hopefully noone was missed from this list. DOWNLOAD: You can download the source or binary packages from: http://www.balabit.com/network-security/syslog-ng/opensource-logging-system… The documentation of the syslog-ng Open Source Edition is available in The syslog-ng Open Source Edition Administrator's Guide at http://www.balabit.com/support/documentation/

1 0