diff options
author | Rainer Gerhards <rgerhards@adiscon.com> | 2005-10-12 14:01:10 +0000 |
---|---|---|
committer | Rainer Gerhards <rgerhards@adiscon.com> | 2005-10-12 14:01:10 +0000 |
commit | 7e10c67a1737d19f5038ad1164b29804d47d9bce (patch) | |
tree | 8425244b156c9ab5ad64c166ee1a60a37bc98933 /doc/rsyslog_stunnel.html | |
parent | 086f821b7049abf10d70c6413ac1cf928257e7cf (diff) | |
download | rsyslog-7e10c67a1737d19f5038ad1164b29804d47d9bce.tar.gz rsyslog-7e10c67a1737d19f5038ad1164b29804d47d9bce.tar.xz rsyslog-7e10c67a1737d19f5038ad1164b29804d47d9bce.zip |
updated doc to reflect 1.11.0
Diffstat (limited to 'doc/rsyslog_stunnel.html')
-rw-r--r-- | doc/rsyslog_stunnel.html | 2 |
1 files changed, 1 insertions, 1 deletions
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.</P>
<h2>Preventing Systems from talking directly to the rsyslog Server</h2>
<P>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.</P>
|