From 7e10c67a1737d19f5038ad1164b29804d47d9bce Mon Sep 17 00:00:00 2001 From: Rainer Gerhards Date: Wed, 12 Oct 2005 14:01:10 +0000 Subject: updated doc to reflect 1.11.0 --- doc/rsyslog_stunnel.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc/rsyslog_stunnel.html') diff --git a/doc/rsyslog_stunnel.html b/doc/rsyslog_stunnel.html index 71bb878d..9d944521 100644 --- a/doc/rsyslog_stunnel.html +++ b/doc/rsyslog_stunnel.html @@ -209,7 +209,7 @@ security-sensitve, you should have a look at the various stunnel settings that help you further secure the system.

Preventing Systems from talking directly to the rsyslog Server

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.

-- cgit