diff options
| -rw-r--r-- | doc/imrelp.html | 2 | ||||
| -rw-r--r-- | doc/omrelp.html | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/doc/imrelp.html b/doc/imrelp.html index 4419cf6d..66e8b054 100644 --- a/doc/imrelp.html +++ b/doc/imrelp.html @@ -69,7 +69,7 @@ a single or multiple fingerprints can be listed. When a non-permitted peer connects, the refusal is logged together with it's fingerprint. So if the administrator knows this was a valid request, he can simple add the fingerprint by copy and -past from the logfile to rsyslog.conf. +paste from the logfile to rsyslog.conf. <br>To specify multiple fingerprints, just enclose them in braces like this: <br>tls.permittedPeer=["SHA1:...1", "SHA1:....2"] diff --git a/doc/omrelp.html b/doc/omrelp.html index a4208355..30ac3daa 100644 --- a/doc/omrelp.html +++ b/doc/omrelp.html @@ -54,7 +54,7 @@ must be used. non-permitted peer is connected to, the refusal is logged together with it's fingerprint. So if the administrator knows this was a valid request, he can simple add the fingerprint by copy and - past from the logfile to rsyslog.conf. It must be noted, though, + paste from the logfile to rsyslog.conf. It must be noted, though, that this situation should usually not happen after initial client setup and administrators should be alert in this case. <br>Note that usually a single remote peer should be all that |