summaryrefslogtreecommitdiffstats
path: root/doc/rsyslog_stunnel.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/rsyslog_stunnel.html')
-rw-r--r--doc/rsyslog_stunnel.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/rsyslog_stunnel.html b/doc/rsyslog_stunnel.html
index f4f82cd0..f0c0b3af 100644
--- a/doc/rsyslog_stunnel.html
+++ b/doc/rsyslog_stunnel.html
@@ -23,7 +23,7 @@ a peek at your data.</b> In some environments, this is no problem at all. In
others, it is a huge setback, probably even preventing deployment of syslog
solutions. Thankfully, there is an easy way to encrypt syslog communication. I
will describe one approach in this paper.</p>
-<p>The most straigthforward solution would be that the syslogd itself encrypts
+<p>The most straightforward solution would be that the syslogd itself encrypts
messages. Unfortuantely, encryption is only standardized in
<a href="http://www.monitorware.com/Common/en/glossary/rfc3195.php">RFC 3195</a>. But there
is currently no syslogd that implements RFC 3195's encryption features,