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

syslog-ng Agent for Windows 4 LTS (4.0.3) has been released
by devel＠balabit.hu 05 Apr '12

05 Apr '12

------------------------------------------------------------------------------ PACKAGE : syslog-ng Agent for Windows VERSION : 4 LTS (4.0.3) SUMMARY : new stable release DATE : Apr 4, 2012 ------------------------------------------------------------------------------ DESCRIPTION: A new stable version of syslog-ng Agent for Windows (4 LTS (4.0.3)) has been released. For latest fixes in the 4.0.x branch you are recommended to upgrade to this version. CHANGES: 4 LTS (4.0.3) Wed, 04 Apr 2012 10:20:55 +0100 WARNING Upgrading to syslog-ng Agent version 4.0.3 is supported only from syslog-ng Agent version 4.0.2. Fixed issues: #25994: Memory leak when using file sources #24545: Using wildcard file sources with lots of files crash the agent #26169: Eventlog messages are not sent if the container is cleared while the agent is stopped #25155: Eventlog Message Templates longer than 255 characters are not inherited to domain members #25993: Reading a corrupt Eventlog entry causes the agent to keep sending the same messages #25935: The .exe installer ignores the /D option on 64-bit systems #26035: Exported XML configuration files include a hardwired path to the XSD schema For details on the fixed issues see our issue tracking page at http://www.balabit.com/mybalabit/fixed_bugs/revision/ UPGRADE: For details on upgrading and possible upgrade paths, read Section 2.4., Upgrading syslog-ng in the The syslog-ng Agent for Windows 4.0 Administrator Guide: http://www.balabit.com/support/documentation/syslog-ng-windows-agent-v4.0-g… 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 4 LTS (4.0.3) Administrator Guide at: http://www.balabit.com/support/documentation/

1 0

syslog-ng Agent for Windows 4 LTS (4.0.3) has been released
by devel＠balabit.hu 05 Apr '12

05 Apr '12

------------------------------------------------------------------------------ PACKAGE : syslog-ng Agent for Windows VERSION : 4 LTS (4.0.3) SUMMARY : new stable release DATE : Apr 5, 2012 ------------------------------------------------------------------------------ DESCRIPTION: A new stable version of syslog-ng Agent for Windows (4 LTS (4.0.3)) has been released. For latest fixes in the 4.0.x branch you are recommended to upgrade to this version. CHANGES: 4 LTS (4.0.3) Wed, 04 Apr 2012 10:20:55 +0100 WARNING Upgrading to syslog-ng Agent version 4.0.3 is supported only from syslog-ng Agent version 4.0.2. Fixed issues: #25994: Memory leak when using file sources #24545: Using wildcard file sources with lots of files crash the agent #26169: Eventlog messages are not sent if the container is cleared while the agent is stopped #25155: Eventlog Message Templates longer than 255 characters are not inherited to domain members #25993: Reading a corrupt Eventlog entry causes the agent to keep sending the same messages #25935: The .exe installer ignores the /D option on 64-bit systems #26035: Exported XML configuration files include a hardwired path to the XSD schema For details on the fixed issues see our issue tracking page at http://www.balabit.com/mybalabit/fixed_bugs/revision/ UPGRADE: For details on upgrading and possible upgrade paths, read Section 2.4., Upgrading syslog-ng in the The syslog-ng Agent for Windows 4.0 Administrator Guide: http://www.balabit.com/support/documentation/syslog-ng-windows-agent-v4.0-g… 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 4 LTS (4.0.3) Administrator Guide at: http://www.balabit.com/support/documentation/

1 0

syslog-ng Premium Edition 4 F2 (4.2.2) has been released
by devel＠balabit.hu 22 Mar '12

22 Mar '12

------------------------------------------------------------------------------ PACKAGE : syslog-ng Premium Edition VERSION : 4 F2 (4.2.2) SUMMARY : New syslog-ng Premium Edition feature release DATE : Mar 22, 2012 ------------------------------------------------------------------------------ DESCRIPTION: A new version of syslog-ng Premium Edition 4 F2 (4 F2 (4.2.2)) has been released. For latest fixes in the 4 F2 (4.2.x) branch you are recommended to upgrade to this version. CHANGES: 4 F2 (4.2.2) Thu, 22 Mar 2012 14:08:00 +0200 New features: * Starting with version 4 F2 (4.2.2), on-the-wire compression can be enabled in TLS-encrypted communication to reduce the bandwidth usage of transporting log messages. Note that this option must be enabled both on the server and the client side to have any effect. Enabling compression can significantly reduce the bandwidth required to transport the messages, but can slightly decrease the performance of syslog-ng PE, reducing the number of transferred messages. Fixed issues: #26029: syslog-ng crashes when pipe destination receives an EAGAIN signal #25972: Using a CSV parser in multiple logpaths does not have effect #26127: syslog-ng is leaking file descriptors #26128: The syslog-ng server leaks memory after closing many TLS connections #26077: SQL destination with an empty indexes() option causes syslog-ng to crash after reload For details on the fixed issues see our new issue tracking page at https://www.balabit.com/mybalabit/fixed_bugs/revision/ DOWNLOAD: Download the latest binaries from: http://www.balabit.com/network-security/syslog-ng/central-syslog-server/sup… 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 Premium Edition 4 F2 (4.2.2) Administrator Guide at: http://www.balabit.com/network-security/syslog-ng/central-syslog-server/sup… Kind Regards, BalaBit IT Security

1 0

syslog-ng Premium Edition 4 LTS (4.0.5) has been released
by devel＠balabit.hu 12 Mar '12

12 Mar '12

------------------------------------------------------------------------------ PACKAGE : syslog-ng Premium Edition VERSION : 4 LTS (4.0.5) SUMMARY : new stable release DATE : Mar 9, 2012 ------------------------------------------------------------------------------ DESCRIPTION: A new stable version of syslog-ng Premium Edition (4 LTS (4.0.5)) has been released. For a full description on stable and feature releases, see Section 2.16. Stable and feature releases of syslog-ng PE in The syslog-ng Premium Edition 4 LTS (4.0.5) Administrator Guide. CHANGES: 4 LTS (4.0.5) Fri, 09 Mar 2012 13:26:48 +0100 Fixed issues: #25577: Fixed a syslog-ng deadlock in case of failed SQL transactions #24425: In rare cases, syslog-ng crashes on Solaris #24546: Memory leak when reading from disk buffer #24210: The lgstool tail command fails with an error message #22763: The trusted-keys() option is ignored if the value was not an SHA1 key #23297: SQL: messages lost from FIFO when reloading syslog-ng #23308: SQL: When shutting down syslog-ng, messages from FIFO are lost #23110: Debug logs of syslog-ng include every modification of the log messages #23176: syslog-ng removes the PRI value if it is 0 #23409: Reading from files using the wildcard file source is slow #25963: syslog-ng does not start if the persist file is invalid #23114: A single log message is not sent using TLS, two messages are required #23418: Losing messages when flow-control is enabled #23555: syslog-ng crashes when the pad_size() is longer than the message #22636: The unix-stream and dgram drivers duplicate messages in some cases #25956: syslog-ng stops processing messages when the timestamping server is slow #25978: Receiving messages from obsolete network sources causes a segfault #25979: Rewrite: Attempting to rewrite a read-only field overwrites the MESSAGE field #25995: When reloading the configuration is not successful, syslog-ng can duplicate log messages #22693: In some cases the disk buffer file becomes unreadable #24580: If the flush_timeout() is low, the throttle option is not working for file destinations CHANGES: Deadlock detection: * The supervisor process of syslog-ng can automatically check if syslog-ng entered a deadlock and does not respond. If the syslog-ng process does not respond, the supervisor process restarts syslog-ng. By default, the supervisor process checks for timeouts every 300 seconds. To modify this value, use the '--deadlock-check-timeout' or '-D' command-line option of syslog-ng For details on the fixed issues see our new issue tracking page at https://www.balabit.com/mybalabit/fixed_bugs/revision/ The documentation of syslog-ng 4 LTS, including the installation and user guides is available in PDF, HTML, and single-page HTML format at: http://www.balabit.com/support/documentation/ UPGRADE: For details on upgrading and possible upgrade paths, read Section 3.5., Upgrading syslog-ng in the The syslog-ng Premium Edition 4 LTS Administrator Guide: http://www.balabit.com/support/documentation/syslog-ng-pe-v4.0-guide-admin-… Kind Regards, BalaBit IT Security 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 Premium Edition 4 LTS (4.0.5) Administrator Guide at: http://www.balabit.com/support/documentation/

1 0

syslog-ng 3.4.0alpha1 has been released
by devel＠balabit.hu 11 Mar '12

11 Mar '12

------------------------------------------------------------------------------ PACKAGE : syslog-ng VERSION : 3.4.0alpha1 SUMMARY : new stable release DATE : Mar 11, 2012 ------------------------------------------------------------------------------ DESCRIPTION: A new stable version of syslog-ng Open Source Edition (3.4.0alpha1) has been released. This is an alpha release aiming at collecting feedback and testing on the upcoming 3.4 version. Use in production environments is not recommended. CHANGES: 3.4.0alpha1 Features: ========= * Support for junctions & channels were added, which improve the flexibility of the syslog-ng configuration language. This allows combining sources with their closely tied processing functionality (like parser, rewrite and filter statements). Read this blog post for more information: http://bazsi.blogs.balabit.com/2012/01/syslog-ng-flexibility-improvements/ In the final form of the functionality the "log" keyword as described in the blog post above was replaced with "channel". * The functionality to query and manipulate sets of name-value pairs (often referenced as value-pairs and used in the mongodb() destination driver and the $(format-json) template function). got significantly improved. It is now possible to change the name of the keys when creating the output. See this commit for more information: https://github.com/bazsi/syslog-ng-3.4/commit/ddc7c2539bd66fa35e8df441e4baf… * Plugins & modules are now demand-loaded automatically if the "autoload-compiled-modules" global variable is set to 1, which is the default. Any shared libraries found on the module search path is considered for loading if the configuration file contains a reference to a functionality it provides. To disable this functionality simply set the referenced variable to 0 with a "@define" statement and load modules explicitly via "@module" statements. To list the available plugins & modules, use the --module-registry command line option for syslog-ng, which results in a detailed listing. * Added a new parser named json-parser() to parse incoming JSON formatted messages. See this commit for more information: https://github.com/bazsi/syslog-ng-3.4/commit/e5569687bba2551c89a78faee55bc… * Added a number of template functions: $(length ARG) - length of a template expression $(substr ARG START [LEN]) - substring of a string $(strip ARG) - remove white space from the start and end $(sanitize ARG1 ARG2) - join args to form a filename while removing special characters like '/' $(+), $(-), $(*), $(/), $(%) - perform numeric operations * Added support for replicasets to the mongodb() destination driver. https://github.com/bazsi/syslog-ng-3.4/commit/a980b9d268efa54879d3deeb4a53f… * Added support for safe-mode() to the mongodb() destination driver that ensures inserts were properly executed at the cost of some performance penalties. https://github.com/bazsi/syslog-ng-3.4/commit/768f0c6ec8eba2ad51531f2331fb5… * Added support for SMTP destination to send out emails triggered by log messages. https://github.com/bazsi/syslog-ng-3.4/commit/404ceb959efe9715ce7437d7dcdc2… * Added support for generating UUIDs via the $(uuid) template function. https://github.com/bazsi/syslog-ng-3.4/commit/a16798c653c057239236945034114… * Added the @SET@ parser to db-parser(). https://github.com/bazsi/syslog-ng-3.4/commit/ab08c84abbeda5a200b8150a6af7b… * Added support for dbd-option() in the sql() destination driver that makes it possible to supply driver specific options to the DBI driver. https://github.com/bazsi/syslog-ng-3.4/commit/9254fe9e6236746bf1f955f0cac12… * Reload of the configuration can now be triggered using "syslog-ng-ctl reload". * A new macro named $LOGHOST was added, which expands to the local hostname running syslog-ng. * A set of time macros were added prefixed with "C_" that use the current time instead of the reception time (prefixed R_) and and the time that was included in the message (prefixed S_). This means that C_DATE expands to the current date, whereas R_DATE would expand to the date the current message was received at. https://github.com/bazsi/syslog-ng-3.4/commit/c2d17009e2ce14960acb519750fe2… * Improved error reporting by including the configuration-file location of the object associated with the error. This makes it easier to diagnose errors even in the case of otherwise unnamed objects. * This release also includes all fixes of the 3.3 branch, which are not listed here for brevity's sake. The merged commit ID is: bf742b0, which is a couple of patches ahead of "3.3.4". Credits: ======== syslog-ng is developed as a community project, and as such it relies on volunteers to do the work necessarily to produce syslog-ng. Reporting bugs, testing changes, writing code or simply providing feedback are all important contributions, so please if you are a user of syslog-ng, contribute. These people have helped in this release: Andreas Piesk Balazs Scheidler (BalaBit) Balint Kovacs (BalaBit) Evan Rempel (University of Victoria) Gergely Nagy (BalaBit) Heiko Gerstung Hendrik Völker (Verizon) Jakub Jankowski (superhost.pl) Martin Grauel (BalaBit) Matthias Runge (Fedora) Patrick Hemmer Russ Milne (Seccuris) 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

syslog-ng Premium Edition 4 F2 (4.2.1) has been released
by devel＠balabit.hu 29 Feb '12

29 Feb '12

------------------------------------------------------------------------------ PACKAGE : syslog-ng Premium Edition VERSION : 4 F2 (4.2.1) SUMMARY : New syslog-ng Premium Edition feature release DATE : Feb 20, 2012 ------------------------------------------------------------------------------ Dear syslog-ng Premium Edition Users, A new feature version of the syslog-ng Premium Edition (PE) has been released. The main new features of syslog-ng Premium Edition 4 F2 (4.2.1) are briefly summarized below: WARNING New license required for multi-CPU operation Note that version 4 F2 of syslog-ng Premium Edition includes multi-threaded processing with a 2 CPU core limit. If you are upgrading your syslog-ng PE server from version 4.1 to 4.2 and your syslog-ng PE deployment requires more than 2 CPU cores, you will need to obtain a new license file, free of charge, from the BalaBit sales department. Reliable disk-based buffering * Reliable disk-based buffering is now available in syslog-ng PE. Use reliable disk-based buffering if you do not want to lose logs in case of reload/restart, unreachable destination or syslog-ng PE crash. This solution provides a slower, but reliable disk-buffer option. The disk-buffer file is created and initialized at startup and gradually grows as new messages arrive. Collecting messages from tables or relational database * Starting with version 4 F2, the syslog-ng PE application is able to collect messages from tables or relational database, using the sql() driver. Currently the Microsoft SQL (MSSQL), MySQL, Oracle and PostgreSQL databases are supported. The syslog-ng PE application can connect to a database, collect records from a table and then create a message from each record. Every query executed by the SQL source can be customized. Reliable Log Transfer Protocol * The syslog-ng application can send and receive log messages in a reliable way over the TCP transport layer using the Reliable Log Transfer Protocol (RLTP). RLTP is a new transport protocol that prevents message loss during connection breaks. It detects the last received message on the receiving end and then starts resending messages from that point. Therefore, messages are not duplicated at the receiving end in case of a connection break. It also allows the negotiation of using TLS with a single source driver. New hard macro: Unique receipt ID * A unique ID for messages generated at reception time on the receiving host. It facilitates defining relationships between messages that are potentially distributed to different files on the same host, or different hosts. Installation path in .RUN installer * The syslog-ng PE application can be installed to an alternative location. It can be useful if the user intends to install syslog-ng PE without registering it as a service, or if it cannot be installed to the default location because of policy compliance reasons. Other changes * Starting with version 4 F2, lgstool cat and lgstool tail --filter option is available. * From 4 F2, syslog-ng PE will limit the number of processors/cores used by syslog-ng PE. It is limited in the license file, through the Max-Processors entry. If you are upgrading your syslog-ng server from version 4.1 to 4.2 and your syslog-ng deployment requires more than 2 CPU cores, you will need to obtain a new license file, free of charge, from the BalaBit sales department. Please contact the sales department at sales(a)balabit.com * AIX 7.1 has been added to the list of supported platforms Fixed issues: #25840: invalid frame header sent by syslog-ng #24459: Possible segmentation fault in case of a partial write in file destinations #24385: Throttle is not working in tcp destination if disk-buffer is used #25724: The -Q command line option of the syslog-ng binary is functional again #24544: Fixed rewrite rule evaluation in case they were referenced from multiple locations #25578: Fixed a syslog-ng deadlock in case of failed SQL transactions For details on the fixed issues see our new issue tracking page at https://www.balabit.com/mybalabit/fixed_bugs/revision/syslog-ng%204.2.1 The documentation of syslog-ng Premium Edition 4 F2, is available in PDF, HTML, and single-page HTML format at: http://www.balabit.com/network-security/syslog-ng/central-syslog-server/sup… UPGRADE: For details on upgrading and possible upgrade paths, read Section Upgrading syslog-ng in the The syslog-ng Premium Edition 4 F2 Administrator Guide: http://www.balabit.com/sites/default/files/documents/syslog-ng-pe-4.2-guide… DOWNLOAD: Download the latest binaries from: http://www.balabit.com/network-security/syslog-ng/central-syslog-server/sup… Note that to download the binaries, you have to login into your MyBalaBit account. Kind Regards, BalaBit IT Security

1 0

Re: [syslog-ng-announce] [syslog-ng] syslog-ng 3.3.4 has been released
by BalaBit Development Team 22 Jan '12

22 Jan '12

On Fri, 2012-01-20 at 10:25 +0000, Dave Haywood wrote: > On 19/01/2012 18:51, devel(a)balabit.hu wrote: > > ------------------------------------------------------------------------------ > > PACKAGE : syslog-ng > > VERSION : 3.3.4 > > SUMMARY : new stable release > > DATE : Jan 19, 2012 > > ------------------------------------------------------------------------------ > > > > DESCRIPTION: > > > > A new stable version of syslog-ng Open Source Edition (3.3.4) has > > been > > released. For latest fixes in the 3.3.x feature branch you are > > recommended to > > upgrade to this version. > > I updated my local git tree and I don't see a tag for 3.3.4? > > $ git tag > v2.1.1 > v2.1alpha1 > v2.1beta1 > v2.1beta2 > v3.0.1 > v3.0.2 > v3.1.0 > v3.1beta1 > v3.1beta2 > v3.2alpha1 > v3.2beta1 > v3.3.0alpha1 > v3.3.0alpha2 > v3.3.0beta2 > v3.3.1 > v3.3.2 > > It would be really useful if you could tag it or post the commit ref > that 3.3.4 relates to? I did a "git pull" which, afaik, pulls the > tags too. > Did that, thanks. Seems my VPN connection wasn't alive when I did the release, thus it didn't get pushed. But I've now pushed all tags to both git.balabit.hu and github.com

1 0

syslog-ng 3.3.4 has been released
by devel＠balabit.hu 19 Jan '12

19 Jan '12

------------------------------------------------------------------------------ PACKAGE : syslog-ng VERSION : 3.3.4 SUMMARY : new stable release DATE : Jan 19, 2012 ------------------------------------------------------------------------------ DESCRIPTION: A new stable version of syslog-ng Open Source Edition (3.3.4) has been released. For latest fixes in the 3.3.x feature branch you are recommended to upgrade to this version. CHANGES: 3.3.4 Mon, 16 Jan 2012 23:07:46 +0100 Highlights ========== This release is aimed fixing bugs in the 3.3.x series, with one more important change: there's an incompatible change in the processing of <action> tags in the db-parser() database format (aka patterndb), see below for more details. Bugfixes: ========= * Fixed set() and subst() rewrite operations to work properly on the value() parameter specified in the configuration even if they are referenced at multiple spots in the configuration file. Earlier the 2nd and subsequent invocation of the rewrite rule changed $MESSAGE. * Fixed csv-parser() to work even if it is invoked at multiple spots in the configuration file. Earlier, the 2nd and subsequent references of the parser rule forgot the list of column names and the input template. * Fixed the processing of condition() parameter in rewrite rules, which was broken if it contained a filter() function call. * Fixed program() destination to properly kill the child process on reload and shutdown. * Fixed a potential division by zero error which could happen for large data rates due to a race in an unlocked region. * Fixed an assertion failure in mongodb destination that happened due to a race condition at high data rates. * Fixed an fd leak in the control socket code, that caused the control connection file descriptors to be leaked. Other changes ============= * db-parser() automatically sets a tag named '.classifier.unknown' if the message doesn't match. * The use of actions in db-parser() for messages without a correllation context was inconsistently indexing messages. For actions in rules that had correllation @0 was the new message being generated, and @1 was the message that triggered the rule. Without correllation @0 was used for the triggering message, which is greatly inconsistent and unintuitive. This was fixed by changing the behaviour for rules without correllation, now both correllation and non-correllation rules use @0 for the new message, and @1 for the triggering message. This is an incompatible change in the db-parser() format. * The value of the $TAGS macro is added to pdbtool match output. * unix-dgram() and unix-stream() error logging on systemd failures became more detailed for easier troubleshooting. Credits: ======== syslog-ng is developed as a community project, and as such it relies on volunteers to do the work necessarily to produce syslog-ng. Reporting bugs, testing changes, writing code or simply providing feedback are all important contributions, so please if you are a user of syslog-ng, contribute. These people have helped in this release: Attila M. Magyar (BalaBit) Balazs Scheidler (BalaBit) Costa Farber Dmitry Gilev Evan Rempel (University of Victoria) Fried Zoltan (BalaBit) Gergely Nagy (BalaBit) Jakub Jankowski (SuperHost.pl) John Morrissey (Horde.net) Michael Hocke (New York University) Michal Schmidt (RedHat) Peter Eisenlohr (Inform Software) Svante Signell (Telia.se) Thomas Wollner 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

syslog-ng Premium Edition 3.0 support ended on January 31, 2012
by devel＠balabit.hu 13 Dec '11

13 Dec '11

------------------------------------------------------------------------------ PACKAGE : syslog-ng Premium Edition VERSION : 3.0 SUMMARY : syslog-ng PE 3.0 end of support on January 31, 2012 DATE : Dec 13, 2011 ------------------------------------------------------------------------------ 3.0 Tue, 13 Dec 2011 13:26:48 +0100 DESCRIPTION: The support for syslog-ng Premium Edition 3.0 ends on January 31, 2012. Updates, security fixes, and technical support of syslog-ng 3.0 will be discontinued at this date. You are recommended to upgrade to syslog-ng 4.0 before the support for version 3.0 ends. Version 3.0 of syslog-ng Premium Edition is a stable release, that is supported only for 3 years after its original publication date and for 1 year after the next LTS release is published (whichever date is later). For details about stable and feature releases, see http://www.balabit.com/dl/html/syslog-ng-pe-v4.0-guide-admin-en.html/concep… UPGRADING: In order to upgrade to syslog-ng Premium Edition 4.0, login to your MyBalabit account at http://www.balabit.com/mybalabit/ and download the new binary packages. After that, follow the installation procedure described in Chapter 3, Installing syslog-ng in The syslog-ng Premium Edition 4.0 Administrator Guide (available at http://www.balabit.com/support/documentation/) The installer will automatically recognize earlier installations of syslog-ng, and offer to re-use the syslog-ng configuration file and the license. 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 Premium Edition 4 F1 (4.1.3) has been released
by devel＠balabit.hu 06 Dec '11

06 Dec '11

------------------------------------------------------------------------------ PACKAGE : syslog-ng Premium Edition VERSION : 4 F1 (4.1.3) SUMMARY : New syslog-ng Premium Edition feature release DATE : Dec 6, 2011 ------------------------------------------------------------------------------ DESCRIPTION: A new version of syslog-ng Premium Edition 4 F1 (4 F1 (4.1.3)) has been released. For latest fixes in the 4 F1 (4.1.x) branch you are recommended to upgrade to this version. CHANGES: 4 F1 (4.1.3) Tue, 06 Dec 2011 13:26:48 +0100 Fixed issues: #25145: Timestamps on logstores are empty For details on the fixed issues see our new issue tracking page at https://www.balabit.com/mybalabit/fixed_bugs/revision/ The documentation of syslog-ng 4 F1, including the installation and user guides is available in PDF, HTML, and single-page HTML format at: http://www.balabit.com/support/documentation/ UPGRADE: For details on upgrading and possible upgrade paths, read Section 3.4., Upgrading syslog-ng in the The syslog-ng Premium Edition 4 F1 Administrator Guide: http://www.balabit.com/support/documentation/syslog-ng-pe-v4.1-guide-admin-… Kind Regards, BalaBit IT Security DOWNLOAD: Download the latest binaries from: http://www.balabit.com/network-security/syslog-ng/central-syslog-server/sup… 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 Premium Edition 4 F1 (4.1.3) Administrator Guide at: http://www.balabit.hu/support/documentation?&product_line=46&product_type=48

1 0