January 2010 - syslog-ng-announce

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

27 Jan '10

------------------------------------------------------------------------------ PACKAGE : syslog-ng Agent for Windows VERSION : 3.0.7 SUMMARY : new stable release DATE : Jan 26, 2010 ------------------------------------------------------------------------------ DESCRIPTION: A new stable version of syslog-ng Agent for Windows (3.0.7) has been released. For latest fixes in the 3.0.x branch you are recommended to upgrade to this version. CHANGES: 3.0.7 Tue, 1 Dec 2009 10:20:55 +0100 Core: * The syslog-ng Agent for Windows application now adds the version number to its configuration stored in the registry. This will help to avoid problems during later upgrades to future versions, e.g., to 3.1. Upgrading to syslog-ng Agent version 3.1 will be supported only from syslog-ng Agent version 3.0.7. * 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. * 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. 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 * 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.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