diff options
author | Rich Salz <rsalz@akamai.com> | 2015-08-17 15:21:33 -0400 |
---|---|---|
committer | Rich Salz <rsalz@openssl.org> | 2015-08-21 15:11:50 -0400 |
commit | 9b86974e0c705ea321ddbc9a9d8562c894809e5b (patch) | |
tree | 69b6437896ca7728ebec6b7d3be7b217149d9862 /doc/apps/s_time.pod | |
parent | 3da9505dc02b0594633c73a11343f54bb5dbf536 (diff) |
Fix L<> content in manpages
L<foo|foo> is sub-optimal If the xref is the same as the title,
which is what we do, then you only need L<foo>. This fixes all
1457 occurrences in 349 files. Approximately. (And pod used to
need both.)
Reviewed-by: Richard Levitte <levitte@openssl.org>
Diffstat (limited to 'doc/apps/s_time.pod')
-rw-r--r-- | doc/apps/s_time.pod | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/doc/apps/s_time.pod b/doc/apps/s_time.pod index b8dad09a03..50ac0e09fa 100644 --- a/doc/apps/s_time.pod +++ b/doc/apps/s_time.pod @@ -97,7 +97,7 @@ these options disable the use of certain SSL or TLS protocols. By default the initial handshake uses a method which should be compatible with all servers and permit them to use SSL v3 or TLS as appropriate. The timing program is not as rich in options to turn protocols on and off as -the L<s_client(1)|s_client(1)> program and may not connect to all servers. +the L<s_client(1)> program and may not connect to all servers. Unfortunately there are a lot of ancient and broken servers in use which cannot handle this technique and will fail to connect. Some servers only @@ -113,7 +113,7 @@ option enables various workarounds. this allows the cipher list sent by the client to be modified. Although the server determines which cipher suite is used it should take the first supported cipher in the list sent by the client. -See the L<ciphers(1)|ciphers(1)> command for more information. +See the L<ciphers(1)> command for more information. =item B<-time length> @@ -131,7 +131,7 @@ To connect to an SSL HTTP server and get the default page the command openssl s_time -connect servername:443 -www / -CApath yourdir -CAfile yourfile.pem -cipher commoncipher [-ssl3] would typically be used (https uses port 443). 'commoncipher' is a cipher to -which both client and server can agree, see the L<ciphers(1)|ciphers(1)> command +which both client and server can agree, see the L<ciphers(1)> command for details. If the handshake fails then there are several possible causes, if it is @@ -144,10 +144,10 @@ A frequent problem when attempting to get client certificates working is that a web client complains it has no certificates or gives an empty list to choose from. This is normally because the server is not sending the clients certificate authority in its "acceptable CA list" when it -requests a certificate. By using L<s_client(1)|s_client(1)> the CA list can be +requests a certificate. By using L<s_client(1)> the CA list can be viewed and checked. However some servers only request client authentication after a specific URL is requested. To obtain the list in this case it -is necessary to use the B<-prexit> option of L<s_client(1)|s_client(1)> and +is necessary to use the B<-prexit> option of L<s_client(1)> and send an HTTP request for an appropriate page. If a certificate is specified on the command line using the B<-cert> @@ -158,7 +158,7 @@ on the command line is no guarantee that the certificate works. =head1 BUGS Because this program does not have all the options of the -L<s_client(1)|s_client(1)> program to turn protocols on and off, you may not be +L<s_client(1)> program to turn protocols on and off, you may not be able to measure the performance of all protocols with all servers. The B<-verify> option should really exit if the server verification @@ -166,6 +166,6 @@ fails. =head1 SEE ALSO -L<s_client(1)|s_client(1)>, L<s_server(1)|s_server(1)>, L<ciphers(1)|ciphers(1)> +L<s_client(1)>, L<s_server(1)>, L<ciphers(1)> =cut |