1S_TIME(1) OpenSSL S_TIME(1)
2
6 s_time - SSL/TLS performance timing program
7
9 openssl s_time [-connect host:port] [-www page] [-cert filename] [-key
10 filename] [-CApath directory] [-CAfile filename] [-trusted_first]
11 [-reuse] [-new] [-verify depth] [-nbio] [-time seconds] [-ssl3] [-bugs]
12 [-cipher cipherlist]
13
15 The s_time command implements a generic SSL/TLS client which connects
16 to a remote host using SSL/TLS. It can request a page from the server
17 and includes the time to transfer the payload data in its timing
18 measurements. It measures the number of connections within a given
19 timeframe, the amount of data transferred (if any), and calculates the
20 average time spent for one connection.
21
23 -connect host:port
24 This specifies the host and optional port to connect to.
25 -www page
27 This specifies the page to GET from the server. A value of '/' gets
28 the index.htm[l] page. If this parameter is not specified, then
29 s_time will only perform the handshake to establish SSL connections
30 but not transfer any payload data.
31 -cert certname
33 The certificate to use, if one is requested by the server. The
34 default is not to use a certificate. The file is in PEM format.
35 -key keyfile
37 The private key to use. If not specified then the certificate file
38 will be used. The file is in PEM format.
39 -verify depth
41 The verify depth to use. This specifies the maximum length of the
42 server certificate chain and turns on server certificate
43 verification. Currently the verify operation continues after
44 errors so all the problems with a certificate chain can be seen. As
45 a side effect the connection will never fail due to a server
46 certificate verify failure.
47 -CApath directory
49 The directory to use for server certificate verification. This
50 directory must be in "hash format", see verify for more
51 information. These are also used when building the client
52 certificate chain.
53 -CAfile file
55 A file containing trusted certificates to use during server
56 authentication and to use when attempting to build the client
57 certificate chain.
58 -trusted_first
60 Use certificates in CA file or CA directory over the certificates
61 provided by the server when building the trust chain to verify
62 server certificate. This is mainly useful in environments with
63 Bridge CA or Cross-Certified CAs.
64 -new
66 performs the timing test using a new session ID for each
67 connection. If neither -new nor -reuse are specified, they are
68 both on by default and executed in sequence.
69 -reuse
71 performs the timing test using the same session ID; this can be
72 used as a test that session caching is working. If neither -new nor
73 -reuse are specified, they are both on by default and executed in
74 sequence.
75 -nbio
77 turns on non-blocking I/O.
78 -ssl3
80 this option disables the use of certain SSL or TLS protocols. By
81 default the initial handshake uses a method which should be
82 compatible with all servers and permit them to use SSL v3, SSL v2
83 or TLS as appropriate. The timing program is not as rich in
84 options to turn protocols on and off as the s_client(1) program and
85 may not connect to all servers.
86 Unfortunately there are a lot of ancient and broken servers in use
88 which cannot handle this technique and will fail to connect. Some
89 servers only work if TLS is turned off with the -ssl3 option.
90 -bugs
92 there are several known bug in SSL and TLS implementations. Adding
93 this option enables various workarounds.
94 -cipher cipherlist
96 this allows the cipher list sent by the client to be modified.
97 Although the server determines which cipher suite is used it should
98 take the first supported cipher in the list sent by the client.
99 See the ciphers(1) command for more information.
100 -time length
102 specifies how long (in seconds) s_time should establish connections
103 and optionally transfer payload data from a server. Server and
104 client performance and the link speed determine how many
105 connections s_time can establish.
106
108 s_time can be used to measure the performance of an SSL connection. To
109 connect to an SSL HTTP server and get the default page the command
110 openssl s_time -connect servername:443 -www / -CApath yourdir -CAfile yourfile.pem -cipher commoncipher [-ssl3]
112 would typically be used (https uses port 443). 'commoncipher' is a
114 cipher to which both client and server can agree, see the ciphers(1)
115 command for details.
116 If the handshake fails then there are several possible causes, if it is
118 nothing obvious like no client certificate then the -bugs, -ssl3
119 options can be tried in case it is a buggy server. In particular you
120 should play with these options before submitting a bug report to an
121 OpenSSL mailing list.
122 A frequent problem when attempting to get client certificates working
124 is that a web client complains it has no certificates or gives an empty
125 list to choose from. This is normally because the server is not sending
126 the clients certificate authority in its "acceptable CA list" when it
127 requests a certificate. By using s_client(1) the CA list can be viewed
128 and checked. However some servers only request client authentication
129 after a specific URL is requested. To obtain the list in this case it
130 is necessary to use the -prexit option of s_client(1) and send an HTTP
131 request for an appropriate page.
132 If a certificate is specified on the command line using the -cert
134 option it will not be used unless the server specifically requests a
135 client certificate. Therefor merely including a client certificate on
136 the command line is no guarantee that the certificate works.
137
139 Because this program does not have all the options of the s_client(1)
140 program to turn protocols on and off, you may not be able to measure
141 the performance of all protocols with all servers.
142 The -verify option should really exit if the server verification fails.
144
146 s_client(1), s_server(1), ciphers(1)
1471.0.2k 2019-03-12 S_TIME(1)