commit 00f847e472d6492163668ce119efb4d4bd2898d2
parent b69a5fe7ac9a1e5d3278b4dd43a3d829fa6b191f
Author: Robert Russell <robertrussell.72001@gmail.com>
Date: Wed, 17 Jul 2024 16:07:02 -0700
Update man page to meet conventions (again)
Diffstat:
1 file changed, 9 insertions(+), 8 deletions(-)
diff --git a/tlsrp.1 b/tlsrp.1
@@ -15,14 +15,15 @@ Each nonempty line in \fIconfig_path\fR has one of the following formats:
= \fBtcp:\fR[\fIhost\fR]\fB:\fR[\fIport\fR]
| \fBunix:\fIpath\fR
.SH DESCRIPTION
-tlsrp accepts TLS-secured connections on one or more source sockets and tunnels
-the decrypted bytes to one of many sink sockets. tlsrp chooses the certificate
-and sink socket for each client (among those listed in the configuration file)
-based on the hostname specified by the client using the Server Name Indication
-(SNI) TLS extension. More specifically, the first \fBcert\fR (resp.,
-\fBsink\fR) entry in the configuration file that matches the client's requested
-hostname is chosen. Clients without SNI support are handled using the first
-\fBcert\fR entry and the first \fBsink\fR entry in the configuration file.
+\fBtlsrp\fR accepts TLS-secured connections on one or more source sockets and
+tunnels the decrypted bytes to one of many sink sockets. \fBtlsrp\fR chooses
+the certificate and sink socket for each client (among those listed in the
+configuration file) based on the hostname specified by the client using the
+Server Name Indication (SNI) TLS extension. More specifically, the first
+\fBcert\fR (resp., \fBsink\fR) entry in the configuration file that matches
+the client's requested hostname is chosen. Clients without SNI support are
+handled using the first \fBcert\fR entry and the first \fBsink\fR entry in
+the configuration file.
.P
For TCP sinks, \fIhost\fR defaults to the local system. For TCP sources,
\fIhost\fR defaults to all available unicast and anycast IP addresses of the
