rsyslog 3.19.2, a development branch version, has just been released. This version contains a new property "fromhost-ip", which enables to obtain the IP address of the syslog sender irrelevant of the -x option setting. So now both the name and IP address are available. Other than that, the version contains a number of bug fixes, many in the TLS area. This version is a recommended update for all development branch users. It is quite stable. It is not yet suggested to use the TLS functionality outside of test environments.
I have just released rsyslog 2.0.5, an update for the v2-stable branch.
This is primarily a bug fixing release. It solves a problem with regular expression based field-extraction and provides better compatibility with recent versions of liblogging. This update is recommended, but not absolutely necessary if you do not experience any problems with your current v2-stable install.
We have just released rsyslog 3.19.1, an update of the development branch. This version primarily fixes some problems with the build system. There were some files missing, which could result in strange warnings. Also, some minor code cleanup to get rid of some compiler warnings is included. This version is highly recommended for all users of the development branch. Note, however, that it is still not suitable for use on production machines.
It is the first release that natively supports TLS for plain TCP syslog. Actually, it is the world's first implementation of the upcoming syslog-transport-tls IETF standard. As this standard is not yet finished, the implementation is obviously experimental.
Native TLS is a big improvement over existing functionality. For example, rsyslog can now be used without the help of stunnel, which relieves us of some problems from those configurations. To the best of my knowledge, rsyslog is the first open-source syslogd offering TLS support natively.
The current TLS functionality is limited to the bare minimum. During the next few weeks, I will improve it based on my own spec and feedback (hopefully received). My hope is to have a production-grade implementation by summer at latest. Please note rsyslog's premium and ultra-reliable RELP protocol does not yet support TLS (but can be used with stunnel without the real problems legacy tcp had with it). My plan is to let TLS mature with legacy syslog and then move it to RELP. Thus I can limit my development to one major use case, which I think will facilitate things.
There is some documentation on how to use the new TLS mode:
Currently, TLS is provided via GnuTLS. As I outlined earlier on the list, GnuTLS offered much more support to getting started (documentation and sample-code wise). I will focus on GnuTLS until I am fully satisfied with the TLS implementation). I'll then see that I can also integrate NSS. Advise in this regard would be highly welcome, so if you have some knowledge in this area, please contribute.
In order to support TLS (and multiple libraries!), a major rewrite of the networking components has been done. Rsyslog now supports a so-called "network streams" (netstreams) driver interface. This interface enables app-level functionality (like the legacy tcp syslog sender and receiver) to work with dynamically selectable netstream drivers (like plain (unencrypted) TCP) and TLS). This interface will enable rsyslog to utilize other TLS drivers (and even other protocols) in the future. Different drivers can even be used concurrently.
Rsyslog now has been split into a runtime system and tools (with currently rsyslogd being the only tool). This design will further strengthen modularization and help make rsyslog functionality available in small parts.
Finally, the RFC 3195 input has been rewritten in the form of an input plugin. It can now be build as part of the normal build procedure.
Please note that there were a couple of major changes. I expect the initial 3.19.0 to be quite Unstable. I recommend it for testing environments, only. Even those parts that were not directly touched may have become a bit destabilized due to the runtime split. So please use it with care. Feedback, however, would be more than welcome, because I need to start somewhere to stabilize this release. That can only be done with your help. So please use it on test systems, try to break it and file bug reports when it fails.
We have just released rsyslog 3.16.1, a release of the v3-stable branch. This version contains one important bug fix. The imklog input plugin did not correctly start up in some environments and could even cause a segfault. This is now corrected. Upgrading to 3.16.1 is strongly recommended for all users of the v3-stable branch who use imklog.
Version 2.1.0 is the first beta version of the v2 branch. PhpLogCon has been completely rewritten from scratch. It now offers a state-of-the art modern user interface and also is able to work with log files and not just databases. For example, it can be used to view a remote server's log files over the web (proper authentication settings highly recommended).
I have just released rsyslog 3.16.0, a v3-stable release. This release brings a major new feature, RELP support, to the stable branch. RELP enables lossless transmission of syslog messages, in cases where even plain tcp syslog fails. Other than that, the release contains a few bugfixes.
Users of the v3-stable branch are advised to update to the new release.
Rsyslog 3.17.1 has just been released. The primary new feature is full BSD platform support. Rsyslog now not only compiles cleanly on BSD, but also now supports BSD's kernel log natively. In general, kernel logging has been improved and better documented. High-precision timestamps for the kernel log have been enabled. There are also some minor other enhancements as well as a couple of bug fixes. Rsyslog 3.17.1 is a recommended update for all users of the devel branch.
I have just released 3.14.2, an update to v3-stable. It is a purely bug-fixing release. Most importantly, it fixes a problem that caused imklog not to pull module symbols correctly from recent kernels. Also, a segfault caused by using expression-based filters is fixed. There are also some other fixes, see ChangeLog for details. This is a recommended update for all v3-stable branch users.
rsyslog 3.15.1 has been released. This is a refresh of the beta branch, providing new bug fixes. The beta branch currently features the RELP protocol and will be the next v3-stable once it has sufficiently matured.
