diff options
| author | Rainer Gerhards <rgerhards@adiscon.com> | 2009-03-05 10:37:25 +0100 |
|---|---|---|
| committer | Rainer Gerhards <rgerhards@adiscon.com> | 2009-03-05 10:37:25 +0100 |
| commit | c38776af21f0c86cef6f8d01e1ce4d5e4f698113 (patch) | |
| tree | ca5cde465d2c93f4d7422f50a79c386eef0db2dd | |
| parent | 5d4fd0e2ef307d9c37c49272f8f20eaa6d5c4485 (diff) | |
| download | rsyslog-c38776af21f0c86cef6f8d01e1ce4d5e4f698113.tar.gz rsyslog-c38776af21f0c86cef6f8d01e1ce4d5e4f698113.tar.xz rsyslog-c38776af21f0c86cef6f8d01e1ce4d5e4f698113.zip | |
doc typo fix
thanks to Trent W. Buck for alerting me.
| -rw-r--r-- | doc/rsyslog_stunnel.html | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/rsyslog_stunnel.html b/doc/rsyslog_stunnel.html index 104a672e..1d024934 100644 --- a/doc/rsyslog_stunnel.html +++ b/doc/rsyslog_stunnel.html @@ -22,7 +22,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, @@ -237,4 +237,4 @@ comments or find bugs (I *do* bugs - no way... ;)), please <a href="http://www.gnu.org/copyleft/fdl.html"> http://www.gnu.org/copyleft/fdl.html</a>.</p> -</body></html>
\ No newline at end of file +</body></html> |