summaryrefslogtreecommitdiffstats
path: root/doc/tls_cert_scenario.html
diff options
context:
space:
mode:
authorRainer Gerhards <rgerhards@adiscon.com>2008-06-20 11:53:05 +0200
committerRainer Gerhards <rgerhards@adiscon.com>2008-06-20 11:53:05 +0200
commit064574425b38832f94e51fe31a1f6293ad8ac604 (patch)
tree94562699bb16fc2e947d6ab685c6c97915c205f4 /doc/tls_cert_scenario.html
parent083d52c86199f64306f1af058b3d4771a37c342f (diff)
downloadrsyslog-064574425b38832f94e51fe31a1f6293ad8ac604.tar.gz
rsyslog-064574425b38832f94e51fe31a1f6293ad8ac604.tar.xz
rsyslog-064574425b38832f94e51fe31a1f6293ad8ac604.zip
improved TLS doc
also changed samples to 2048 bit keys, because 1024 will soon no longer be considered secure.
Diffstat (limited to 'doc/tls_cert_scenario.html')
-rw-r--r--doc/tls_cert_scenario.html3
1 files changed, 1 insertions, 2 deletions
diff --git a/doc/tls_cert_scenario.html b/doc/tls_cert_scenario.html
index dced5393..7973532b 100644
--- a/doc/tls_cert_scenario.html
+++ b/doc/tls_cert_scenario.html
@@ -42,8 +42,7 @@ hav decided to use ada.example.net because it is in the same local network
segment as the router and so we enjoy TLS' security benefits for forwarding the
router messages inside the corporate network. All systems (except the router) use
<a href="http://www.rsyslog.com/">rsyslog</a> as the syslog software.</p>
-<p>
-<center><img src="tls_cert_100.jpg"></center>
+<p><center><img src="tls_cert_100.jpg"></center>
<p>Please note that the CA must not necessarily be connected to the rest of the
network. Actually, it may be considered a security plus if it is not. If the CA
is reachable via the regular network, it should be sufficiently secured (firewal