From d16264098402ef33e1e5441eb6884e7359ee8add Mon Sep 17 00:00:00 2001 From: Rainer Gerhards Date: Mon, 16 Jul 2007 13:24:19 +0000 Subject: added $AllowedSender patch by mildew@gmail.com --- doc/bugs.html | 12 +----------- doc/contributors.html | 5 +++++ doc/features.html | 3 ++- doc/rsyslog_conf.html | 14 +++++++++++--- 4 files changed, 19 insertions(+), 15 deletions(-) diff --git a/doc/bugs.html b/doc/bugs.html index b441d583..0e6621e2 100644 --- a/doc/bugs.html +++ b/doc/bugs.html @@ -11,19 +11,9 @@ bug tracker at sourceforge.net. This list here contains more architectural things while the bug tracker most often lists things that you will actually experience. Please be sure to visit the bug tracker in addition to this list here.

-

This list has last been updated on 2007-06-28 by +

This list has last been updated on 2007-07-16 by Rainer Gerhards.

rsyslogd

-

AllowedSender and IPv6

-

AllowedSenders currently can be used with IPv4, only. IPv6 senders are always -allowed. If you need access control for IPv6, use iptables. AllowedSender -support for IPv6 will most probably be added. Please note that you can also -disable IPv6 support by specifying -4 on the command line.

-

REPEATED LOG LINES

-

If multiple log lines with the exact same content are received, - the duplicates are NOT suppressed. This is done by sysklogd - in all cases. We plan to add this as an optional feature, - but as of now every line is logged.

EQUALLY-NAMED TEMPLATES

If multiple templates with the SAME name are created, all but the first definition is IGNORED. So you can NOT (yet) replace a diff --git a/doc/contributors.html b/doc/contributors.html index eaab1841..1cfa766f 100644 --- a/doc/contributors.html +++ b/doc/contributors.html @@ -27,6 +27,11 @@ Project Initiator and Maintainer

  • provided patch with regex functionality for filters on 2007-07-14, first seen in 1.16.1
    • +

    mildew@gmail.com

    +

    Last Updated: 2007-07-16

    diff --git a/doc/features.html b/doc/features.html index 02bebabb..f104a2dc 100644 --- a/doc/features.html +++ b/doc/features.html @@ -23,7 +23,8 @@ is going on, you can also subscribe to the ssl-protected syslog (via stunnel)
  • ability to filter on any part of - the message, not just facility and severity
  • support for discarding + the message, not just facility and severity
  • ability to use regular + expressions in filters
  • support for discarding messages based on filters
  • ability to execute shell scripts on received messages
  • control of whether the local hostname or the hostname of the origin of the data is shown as the hostname in the output
  • ability to diff --git a/doc/rsyslog_conf.html b/doc/rsyslog_conf.html index f1165619..262738a0 100644 --- a/doc/rsyslog_conf.html +++ b/doc/rsyslog_conf.html @@ -45,7 +45,10 @@ error message. "ip[/bits]" is a machine or network ip address as in "192.0.2.0/24" or "127.0.0.1". If the "/bits" part is omitted, a single host is assumed (32 bits or mask 255.255.255.255). "/0" is not allowed, because that would match any sending system. If you intend to do that, just remove all $AllowedSender -directives. If more than 32 bits are requested, they are adjusted to 32. +directives. If more than 32 bits are requested with IPv4, they are adjusted to 32. +For IPv6, the limit is 128 for obvious reasons. Hostnames, with and without +wildcards, may also be provided. If so, the result of revers DNS resolution is +used for filtering. Multiple allowed senders can be specified in a comma-delimited list. Also, multiple $AllowedSender lines can be given. They are all combined into one UDP and one TCP list. Performance-wise, it is good to specify those allowed senders @@ -56,13 +59,18 @@ the first action after receiving a message. This keeps the access to potential vulnerable code in rsyslog at a minimum. However, it is still a good idea to impose allowed sender limitations via firewalling.

    WARNING: by UDP design, rsyslogd can not identify a spoofed sender -address in UDP syslog packets. As such, a malicous person could spoof the adress +address in UDP syslog packets. As such, a malicious person could spoof the +address of an allowed sender, send such packets to rsyslogd and rsyslogd would accept them as being from the faked sender. To prevent this, use syslog via TCP exclusively. If you need to use UDP-based syslog, make sure that you do proper egress and ingress filtering at the firewall and router level.

    +

    Rsyslog also detects some kind of malicious reverse DNS entries. In any case, +using DNS names adds an extra layer of vulnerability. We recommend to stick with +hard-coded IP addresses whereever possible.

    An example for an allowed sender list is as follows:

    -

    $AllowedSender UDP, 127.0.0.1, 192.0.2.0/24

    +

    $AllowedSender UDP, 127.0.0.1, 192.0.2.0/24, [::1]/128, +*.example.net, somehost.example.com

    UMASK

    The $umask directive allows to specify the rsyslogd processes' umask. If not specified, the system-provided default is used. The value given must always be a -- cgit v1.2.3