- syslog-ng-announce - lists.balabit.hu

syslog-ng Agent for Windows 3.1.0 has been released
by devel＠balabit.hu 27 Jan '10

27 Jan '10

------------------------------------------------------------------------------ PACKAGE : syslog-ng Agent for Windows VERSION : 3.1.0 SUMMARY : new stable release DATE : Jan 26, 2010 ------------------------------------------------------------------------------ DESCRIPTION: A new stable version of syslog-ng Agent for Windows (3.1.0) has been released. This version contains changes, improvements, and new features. WARNING Upgrading to syslog-ng Agent version 3.1 is supported only from syslog-ng Agent version 3.0.7. CHANGES: NEW FEATURES Core * Snare-compatible log forwarding can be enabled at a single location. * It is now possible to resolve the clients own IP address from DNS and use the resolved hostname as the hostname of the client in the syslog messages. This solve the problem that sometimes the hostname of the client changes depending on whether it is logged into a domain. * It is possible to specify the Distinguished Name (DN) of the certificate to use for TLS-encrypted connections. So far it was possible to specify the Common Name (CN) only. * It is now possible to create whitelist filters to forward only the messages that match the filter. * For troubleshooting purposes, the syslog-ng Agent can provide detailed debug logs about its operation. Setting the Software\\BalaBit\\syslog-ng Agent\\AgentDbgLog registry key to 1 sends the debug logs to the DebugView application, while setting the key to 2 produces a log file called syslog_agent.txt. The log file will be created under the installation directory of the syslog-ng Agent, e.g., under C:\Program Files\BalaBit\syslog-ng Agent. Platform support * Collecting log messages from 32-bit and 64-bit Windows 7 platforms is now supported. Installation * The syslog-ng Agent installer can upgrade the XML configuration file of earlier versions. * The options of the silent installer have been updated to simplify the unattended installation of the syslog-ng Agent. * The installer has several new options to simplify the installation and the upgrade of the syslog-ng Agent in various scenarios. BUGFIXES Core: * In certain situations, the agent terminated unexpectedly if a large number of eventlog sources were registered on the client host. This has been corrected. * The GPO occasionally restarted the syslog-ng Agent if the address of a destination server was very long. This has been corrected. Eventlog Sources: * In case an event container did not exist, the agent sent "Cannot format event log message" messages. Now the nonexistent event container is ignored, and a proper log message is sent to the Application container. File Sources: * Until now, the agent has opened text files in a mode that prevented the file from being deleted. Now the files can be deleted, but the deleting application must ensure that there are no unsent messages in the file to avoid losing messages. 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 3.0 Administrator Guide at: http://www.balabit.com/support/documentation/?product=syslog-ng&type=all&la…

1 0

syslog-ng PE 2.1 support ended on December 31, 2009
by devel 11 Jan '10

11 Jan '10

------------------------------------------------------------------------------ PACKAGE : syslog-ng VERSION : 2.1 SUMMARY : syslog-ng PE 2.1 support ended on December 31, 2009 DATE : January 11, 2010 ------------------------------------------------------------------------------ DESCRIPTION: The support for syslog-ng Premium Edition 2.1 has ended on December 31, 2009. No new updates or security fixes will be released for this version. The technical support of syslog-ng Premium Edition 2.1 has also ceased. This announcement applies to syslog-ng Premium Edition and the syslog-ng Agent for Windows alike. If you have not already done so, you are recommended to upgrade to syslog-ng 3.0 as soon as possible. UPGRADING: For details on upgrading to syslog-ng 3.0, see the What is new in syslog-ng Premium Edition 3.0 document (available at http://www.balabit.com/dl/guides/syslog-ng-v3.0-guide-whatsnew-en.pdf) especially the Upgrading and the Important changes sections. In order to upgrade to syslog-ng Premium Edition 3.0, login to your MyBalabit account at http://www.balabit.com/mybalabit/ and download the new license file and the binary packages. After that, follow the installation procedure described in Chapter 4, Installing syslog-ng in The syslog-ng 3.0 Administrator Guide (available at http://www.balabit.com/dl/guides/syslog-ng-v3.0-guide-admin-en.pdf) The installer will automatically recognize earlier installations of syslog-ng, and offer to re-use the syslog-ng configuration file and the license. It will also display warnings about parameters and the format of the configuration file that have changed since version 2.1. For details on upgrading the syslog-ng Agent for Windows, see Section 5.1.1. Upgrading syslog-ng Agent for Windows 2.x to 3.0.x in The syslog-ng 3.0 Administrator Guide. NOTE: The syslog-ng 3.0 license is available only if you have valid software subscription. In case you do not see the new license under your MyBalaBit account, please contact your local distributor, or send an e-mail from the address used in your MyBalaBit registration to Ms. Edit Tusjak at edit.tusjak(a)balabit.com

1 0

syslog-ng OSE 3.1beta2 released
by Balazs Scheidler 18 Dec '09

18 Dec '09

Dear syslog-ng users, A new beta version of the current syslog-ng feature release has been uploaded to our website. https://www.balabit.com/network-security/syslog-ng/opensource-logging-syste… This is a bugfix only release containing blocker issues found in the past three weeks. Please see the NEWS entry below for more details. Any kind of feedback, be it positive or negative is appreciated. 3.1beta2 Fri, 18 Dec 2009 09:19:39 +0100 Bugfixes: * Fixed two major memory leaks, one on input messages, one in patterndb. * Fixed escaped structured data processing. * Fixed expanding SDATA references in templates which have multiple dots in its name (e.g. when an OID is present in the name of the SD param or SD-ID. * pdbtool now correctly zero pads month and day fields in publish date of the merged patterndb file. * pdbtool won't link to unnecessary libraries, which fixes a compilation problem on Solaris with flex installed. -- Bazsi

1 0

syslog-ng Premium Edition 3.0.4 has been released
by devel＠balabit.hu 18 Dec '09

18 Dec '09

------------------------------------------------------------------------------ PACKAGE : syslog-ng Premium Edition VERSION : 3.0.4 SUMMARY : new stable release DATE : Dec 18, 2009 ------------------------------------------------------------------------------ DESCRIPTION: A new stable version of syslog-ng Premium Edition (3.0.4) has been released. For latest fixes in the 3.0.x branch you are recommended to upgrade to this version. CHANGES: 3.0.4 Fri, 18 Dec 2009 16:14:17 +0100 Bugfixes: * Fixed the reception of empty messages received using the syslog driver in RFC5424 format, syslog-ng didn't accept well formed messages that lacked the message portion. * Fixed the handling of empty lines when sending them out using the syslog() driver. The output format lacked a space before the message portion. * The flow-control flag was erroneously enabled if any of the log statements contained either "final" or "fallback". * Fixed a possible 100% CPU usage in case an udp destination went down. * Fixed a FreeBSD init script problem that caused syslog-ng not to start up properly on boot. * Fixed the default value of follow_freq() on FreeBSD's kernel source /dev/klog. * Fixed a possible segfault in SIGHUP processing if an included file contains a syntax error. * Fixed the SQL destination to avoid dropping the output queue in case a HUP was received and no disk buffer is configured. * Fixed rewrite processing, in some cases a rewritten value could be propagated to wrong branches in the log processing tree. * Fixed escaped structured data processing in RFC 5424 messages. * logcat and lgstool asked the passphrase protecting the private key multiple times. This behaviour has been fixed. * Previously if the SQL INSERT statement failed for a log message, syslog-ng repeated the operation indefinitely in the hope that the error would be interim. This has been changed to drop the offending log message after being tried 3 times to avoid clogging the SQL destination. * The incoming TCP connection is dropped in case character encoding problems are encountered. * Fixed CRL validation in "lgstool validate". * Fixed command line processing problems in lgstool that caused lgstool to exit abnormally in case of syntactically incorrect parameters were specified. Installer / init script: * The .run installer changes service registration, it now sets syslog-ng to automatic restart mode by passing the -R argument to mkssys. * Fixed svcadm refresh problem in the Solaris 10 svc method script, which didn't successfully reload syslog-ng previously. 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 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 OSE 3.0.5 released
by Balazs Scheidler 09 Dec '09

09 Dec '09

Dear syslog-ng users, I've uploaded syslog-ng OSE 3.0.5 to our webservers recently which has some quite important bugfixes. I'd recommend any serious deployment of syslog-ng 3.x to upgrade to this release. The results of the last four months were accumulated into this release. Some statistics for those who like them: 37 files changed, 885 insertions(+), 468 deletions(-) In this timespan, altogether 36 patches were produced by the following people: Anthony Lineham (1) Balazs Scheidler (25) Marton Illes (2) Tamas Pal (3) Tevesz Andras (4) Viktor Tusa (1) Some of the bugreporters and testers also deserve credit, who were: Tamas Monos Sandor Geller Imre Lazar Arkadiusz Miśkiewicz Elan Ruusamäe Thank you for your contribution. Also please note that a new feature release of syslog-ng was published in recent weeks, numbered version 3.1beta1. That beta version has improvements in various areas you might want to check out. We'll only include bugfixes in syslog-ng 3.0.x in the future. The list of changes: 3.0.5 Thu, 03 Dec 2009 18:02:56 +0100 Bugfixes: * Fixed a possible hang that caused syslog-ng to completely stop processing messages, in case SQL destination is enabled in configure. The bug does not need a working SQL destination. * Fixed a possible 100% CPU usage in case an udp destination went down. * Fixed host_override/program_override options that were broken in 3.0.4. * Fixed the SQL destination to avoid dropping the output queue in case a HUP was received. * Fixed a possible segmentation fault when parsing syntactically incorrect patterndb files. * Fixed ESTRING parser to include the ending quote character in the result. * Report an error in case there's no terminating brace in template macro references, e.g. no closing brace in ${macro} format. * Fixed FreeBSD init script to add $prefix/sbin to the PATH environment variable. This problem caused syslog-ng not to start up on boot. * Fixed FreeBSD /dev/klog message reading, follow_freq() needs to default to zero in this case (just like Linux /proc/kmsg). * Fixed a possible segfault in SIGHUP processing if an included file contains a syntax error. * RFC5424 over UDP erroneously required frame length, just like TCP, this is now fixed. * Fixed HP-UX 11iv2 compilation issue related to pread/pwrite compile errors. * The flow-control flag was erroneously enabled if any of the log statements contained either "final" or "fallback". * Fixed rewrite processing, in some cases a rewritten value could be propagated to wrong branches in the log processing tree. Other changes: * Added support for Cisco ASA timestamps. * Added version checks for PCRE in the configure script. * Integrate with system LSB init scripts a bit better, with 3.0.5 the init script status reports should nicely integrate with the host system. Happy logging, -- Bazsi

1 0

syslog-ng OSE 3.1beta1 released
by Balazs Scheidler 03 Dec '09

03 Dec '09

Dear syslog-ng users, I'm proud to announce that syslog-ng OSE 3.1 has been released and uploaded to our webserver. This version is new in two ways: 1) of course it has new features, see below for the most interesting bits 2) it is a "feature release", which means that once syslog-ng 3.2 or syslog-ng 4.0 is released, the support for this release will be ceased. See our new version policy at this link: https://www.balabit.com/network-security/syslog-ng/opensource-logging-syste… Since the documentation is not yet up to date with this beta release, I'll try to include the most crucial information about the new features right here in this announcement. For those who hurry, here's a link for the source code: https://www.balabit.com/downloads/files/syslog-ng/open-source-edition/3.1be… And here are the binaries for Linux/FreeBSD systems: https://www.balabit.com/network-security/syslog-ng/opensource-logging-syste… Select the Downloads tab, and in the Version selector select 3.1beta1. What is new in syslog-ng OSE 3.1 -------------------------------- * Support for patterndb v3 format, along with a bunch of new parsers: ANYSTRING, IPv6, IPvANY and FLOAT. Patterndb (more exactly the db-parser()) is a high performance message classifier and information extraction tool, that makes it easy to get away from the unstructured nature of syslog. Patterndb has evolved since it was first introduced in syslog-ng 3.0. It is at the 3rd iteration, hopefully slowly reaching its final form. Patterndb in general and the v1 format database is described in the syslog-ng manual at: http://www.balabit.com/dl/html/syslog-ng-admin-guide_en.html/ch02s12.html The XML schemas that describe the different patterndb versions are available in the syslog-ng source tree: http://git.balabit.hu/?p=bazsi/syslog-ng-3.1.git;a=tree;f=doc/xsd;hb=HEAD The changes in the patterndb format as they evolved were described in Marton Illes's blog at http://marci.blogs.balabit.com/2009/06/new-db-parser-format-and-other.html But see the other related posts as well. Old patterndb databases can be converted to the new format by putting them in a directory and using the pdbtool utility using the command: $ pdbtool merge -p /opt/syslog-ng/var/patterndb.xml -D /opt/syslog-ng/etc/patterns.d Assuming the installation prefix of syslog-ng is /opt/syslog-ng Some v2 format patterns are distributed by BalaBit itself for its SSB product, download location: https://www.balabit.com/downloads/files/patterndb/1.0-20081117/patterndb/ You can convert these db files using pdbtool as described above. Work is ongoing to publish a more comprehensive patterndb, but more on that in a separate post. * Added a new "pdbtool" utility to manage patterndb files: convert them from v1 or v2 format, merge mulitple patterndb files into one and look up matching patterns given a specific message. See the manpage and Marci's post: http://marci.blogs.balabit.com/2009/08/db-parser-new-utility-pdbtool.html * Support for message tags: tags can be assigned to log messages as they enter syslog-ng: either by the source driver or via patterndb. Later it these tags can be used for efficient filtering. http://marci.blogs.balabit.com/2009/05/tag-support-in-syslog-ng.html * Added support for rewriting structured data. Earlier structured data fields in the new RFC5424 style syslog protocol were only read-only values that could be referenced in a template, but they couldn't be changed, and neither was it possible to add new fields in an already existing syslog message. Now all these became possible by using the same syntax that didn't work earlier, e.g. rewrite r_sd { set("55555" value(".SDATA.meta.sequenceId")); }; * Macros and name-value pairs got a little tighter integration, in filters where syslog-ng 3.0 was limited to only use name-value pairs, with 3.1 you can also use macros. The following now works: match("<regexp>" value("R_DATE")); syslog-ng is now warning you in case you are using '$' prefix in the value syntax. * Enhanced dynamic name-value performance by a factor of three. The summary says it all, the performance dynamic name-value pairs that the various parsers produce got faster, thus the performance penalty of structuring the incoming messages got smaller. * Some parsers got additional features: NUMBER is now able to parse hexadecimal numbers, ESTRING is now able to search for a sequence of characters as the end of the string. These are patterndb parsers to make it easier to describe log messages. * Added non-standard and non-portable facility codes (range 10-15), decouple syslog-ng facility name information from the system used to compile syslog-ng on. Until this time the facility codes as understood by syslog-ng were dependant on the platform syslog-ng was compiled on. This is not true anymore, syslog-ng comes with its own "facility" code assignments, based on the RFC, and adding some non-standard values found on various UNIX systems. Any feedback, success/failure reports is more than appreciated. -- Bazsi

1 0

syslog-ng Agent for Windows 3.0.6 has been released
by devel＠balabit.hu 24 Nov '09

24 Nov '09

------------------------------------------------------------------------------ PACKAGE : syslog-ng Agent for Windows VERSION : 3.0.6 SUMMARY : new stable release DATE : Nov 24, 2009 ------------------------------------------------------------------------------ DESCRIPTION: A new stable version of syslog-ng Agent for Windows (3.0.6) has been released. For latest fixes in the 3.0.x branch you are recommended to upgrade to this version. CHANGES: Core: * The syslog-ng Agent for Windows application now supports the Windows 2008 R2 platform. * In certain situations, the agent skipped sending a few messages after the eventlog container was emptied. This has been corrected. * The logging of configuration updates when managing the agent from a Domain Controller. Setting the Software\\BalaBit\\syslog-ng Agent\\GpoDbgLog registry key to 1 produces detailed (debug) logs about the process, while setting the key to 2 produces a log file called syslog_gpext.txt. The log file will be created under C:\Windows\System32 or C:\Winnt\system32, depending on the platform. * The agent did not properly handle cases when dll-s referred by eventlog messages were not available. This 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 version 3.0.6 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 Premium Edition 3.0.3 has been released
by devel＠balabit.hu 16 Nov '09

16 Nov '09

------------------------------------------------------------------------------ PACKAGE : syslog-ng Premium Edition VERSION : 3.0.3 SUMMARY : new stable release DATE : Nov 13, 2009 ------------------------------------------------------------------------------ DESCRIPTION: A new stable version of syslog-ng Premium Edition (3.0.3) has been released. For latest fixes in the 3.0.x branch you are recommended to upgrade to this version. NOTE: This is the last release of the syslog-ng Premium Edition 3.0.x branch that contains new features in addition to bugfixes. From now on, 3.0.x releases will be maintenance releases containing only bugfixes; new features will be released in so-called feature releases having 3.x version numbers. For details on the new version and release policy, see http://www.balabit.com/news/334/ CHANGES: IMPORTANT CHANGES: * There was an unintended change in the meaning of command line argument -C (--chroot) and -R (--persist-file) between 2.x and 3.x versions of syslog-ng. This release reverts this change back to the original 2.x behaviour. This is a incompatible change compared against 3.0.2. Please review your startup scripts if you use the -C or -R options. New Features Sources and destinations * A new 'empty-lines' source flag is available to avoid dropping empty log messages. Empty log messages are dropped by default. * Named pipes can be created automatically with the pipe() destination. The filename of the pipes can contain macros as well. * The default priority/facility value of each source can be specified: these default values are applied to messages that do not include priority/facility values. * The default values for SQL columns are being deprecated, please supply SQL schema information explicitly in your SQL destinations. A warning message was added in case you do not have a full schema and rely on the default values. * A new local_time_zone() option has been added to file() and sql() destinations. This option controls the timezone used when expanding the filename/tablename templates. It defaults to the local timezone. Message parsing * Added the "greedy" flags to the csv-parser() which assigns the remaining part of the message to the last column without caring about column separation characters * Added the "drop-invalid" flag to the csv-parser() which makes the parser drop anything that has less columns than expected. Other * The logcat application used to view logstore files has been renamed to lgstool. * The syslog-ng application now integrates better with the default logrotation tools of the various platforms. Previously, certain platforms have not sent a HUP signal to syslog-ng after rotating the log files, causing syslog-ng to write into a temporary file, with the possibility of losing these messages later. This behavior has been corrected: the syslog-ng installer will now create symlinks to receive the HUP signals of the standard logrotation scripts. * To improve the performance of DNS lookups, the dns_cache_hosts file is checked only once per second, not for every DNS lookup. Bugfixes * The frac_digits() option can be used for non-ISO timestamps as well. * Corrections in the init scripts and the rc.d registrations on various platforms. * Performance corrections in the host_override() and program_override() options. * Fixed the handling of door initialization failures on Solaris. * If a file referenced in a file source does not exist, syslog-ng will display an error message in verbose mode. * Using the tcp6() destination caused aborts during startup. This has been corrected. * The usertty() destination now opens the tty in nonblocking mode to avoid blocking on serial lines. * The SOURCEIP macro was not working properly for IPv6 addresses. This has been corrected. * Corrections in the handling of invalid pattern database files. * In certain rare situations, an error in parsing the pattern database file resulted in heap corruption. This has been corrected. * Under high message load, receiving a HUP signal while flow-control was active (not only enabled, but in operation) caused syslog-ng to terminate in certain situations. This has been corrected. * In certain rare situations syslog-ng stopped processing messages, stalling applications logging to syslog and possibly stalling the entire system. This has been corrected. For details, see the public bug report of the error at https://bugzilla.balabit.com/show_bug.cgi?id=48 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 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

Version policy changes
by devel 11 Nov '09

11 Nov '09

Dear syslog-ng users, Until 2009 November, the products of BalaBit had long development cycles and major releases of the stable branch (like 2.0 or 3.1) were supported for years. The maintenance releases (e.g., 2.0.10) of stable branches almost always included enhancements as well as bugfixes. This policy has two main drawbacks: - enhancements and new features could potentially destabilize the stable branch, and - larger, and therefore somewhat riskier changes and new features could be released only in the next major release. Starting from November 2009 this will change for every product: major releases will be feature based and more frequent. To avoid the need to support several different versions in parallel, the following support policy is introduced: Stable versions, denoted by a two-digit version number ending with .0 (e.g., 2.0 or 3.0): Stable branches are supported for at least 1 year, but no more than 2 stable versions of a product are supported at the same time. Maintenance releases to the stable branch will contain only bugfixes. Feature versions, denoted by two-digit version number ending with a non-zero version number (e.g., 3.1, 3.2 and onwards): Feature branches will contain enhancements and new features, presumably 1-3 new feature per release. Only the last of the feature releases is supported (e.g., when a new feature release comes out, the last one becomes unsupported), and the last feature release becomes the new stable release. NOTE: Releases of the feature branch are tested just like the stable releases; they are not "unstable" development snapshots. The difference between earlier major releases and current feature releases is the smaller number of features contained in a release, and the shorter support periods. If an unstable snapshot or alpha/beta/rc release will be released for public testing, it will be always marked explicitly as such. 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. Maintenance releases will have 3 digits in their version number (e.g., 3.1.4), just like previously. Update releases are releases that include only one or two important bugfixes compared to the latest maintenance release, and are marked by an extra letter after the three digit version number (e.g., an update release for release 3.1.7 would be labeled as 3.1.7a). If an update release is published, it is recommended to use it instead of the latest maintenance release. The upgrade page of the product contains the latest versions of the supported branches, including release dates and release notes. The following examples sum up how the version numbers of the future BalaBit releases can be interpreted (the numbers used are for illustration only): 4.0: The current stable release of the product, maintenance releases of this branch will have a third digit (e.g., 4.0.3) 4.0.2: The second maintenance release of the stable 4.0 branch 4.0.2a: The first update release of the second maintenance release of the stable 4.0 branch 4.1: A feature release that is supported only until the release of the next feature release (4.2) 4.1.3: The third maintenance release of the 4.1 feature branch Feature releases and software subscription ------------------------------------------ Buying a BalaBit product allows you to download and use the: current stable release of the product (e.g., 4.0), including its maintenance releases the feature releases of the product (e.g., 4.1, 4.2, etc.). Note that feature releases become unsupported as soon as the next feature release or the next stable release becomes available. Upgrading to the next stable release (e.g., 5.0) requires software subscription. If you plan to use feature releases in a production environment, it is strongly recommended to buy software subscription as well. The first feature release of syslog-ng Premium Edition will be the 3.1 release. Kind Regards, BalaBit

1 0

syslog-ng Agent for Windows 3.0.5 has been released
by devel＠balabit.hu 07 Oct '09

07 Oct '09

------------------------------------------------------------------------------ PACKAGE : syslog-ng Agent for Windows VERSION : 3.0.5 SUMMARY : new stable release DATE : Oct 6, 2009 ------------------------------------------------------------------------------ DESCRIPTION: A new stable version of syslog-ng Agent for Windows (3.0.5) has been released. For latest fixes in the 3.0.x branch you are recommended to upgrade to this version. CHANGES: Core: * The mapping of event types to event severity levels handled certain event types incorrectly on the Windows Vista and Windows 2008 platforms, causing problems when filtering on the severity level of the messages. This has been corrected. * Certain event log parameters were not processed properly on the Windows 2003 platform. This has been corrected. * The syslog-ng Agent terminated unexpectedly in some situations when it was started manually from the Windows Services control panel. This 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 version 3.0.5 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