From 7e10c67a1737d19f5038ad1164b29804d47d9bce Mon Sep 17 00:00:00 2001
From: Rainer Gerhards
+via plain tcp is finally supported, a bit later sending via TCP, too. Starting +with 1.11.0, RFC 3195 is finally support at the receiving side (a.k.a. "listener"). +Support for sending via RFC 3195 is still due. Anyhow, rsyslog has come much +closer to what it name promises.
The next enhancement scheduled is support for the new syslog-protocol internet draft format, not the least to see how easy/complicated it is to implement. We already know that some subleties of syslog-protocol will @@ -42,7 +44,7 @@ we intend to advance the code and introduce new features.
The database support was included so that our web-based syslog interface can be used. This is another open source project which can be found -under http://www.liblogging.org. We highly recommend having a look at +under http://www.phplogcon.org. We highly recommend having a look at it. It might not work for you if you expect thousands of messages per second (because your database won't be able to provide adequate performance), but in many cases it is a very handy analysis and troubleshooting tool. @@ -60,8 +62,10 @@ sizes of 32k and more. This feature has been tested, but by default is turned of (as it has some memory footprint that we didn't want to put on users not actually requiring it). Search the file syslogd.c and search for "IHE" - you will find easy and precise instructions on what you need to change (it's just -one line of code!). -
Be sure to visit Rainer's syslog block +one line of code!). Please note that RFC 3195/COOKED supports 1K message sizes +only. It'll probably support longer messages in the future, but it is our +believe that using larger messages with current RFC 3195 is a violation of the +standard.
Be sure to visit Rainer's syslog block to get some more insight into the development of rsyslog and syslog in general.
It is possible that remote systems (or attackers) talk to the rsyslog server -by directly connecting to its port 61514. Currently (Jule of 2005), rsyslog does +by directly connecting to its port 61514. Currently (July of 2005), rsyslog does not offer the ability to bind to the local host, only. This feature is planned, but as long as it is missing, rsyslog must be protected via a firewall. This can easily be done via e.g iptables. Just be sure not to forget it.
diff --git a/doc/status.html b/doc/status.html index 6378c2cb..92e13965 100644 --- a/doc/status.html +++ b/doc/status.html @@ -4,10 +4,10 @@This page reflects the status as of 2005-09-27.
+This page reflects the status as of 2005-10-12.
development: 1.10.2 - change log - -download
+development: 1.11.0 - change log - +download
stable: 1.0.2 - change log - download
-- cgit