1S_TIME(1) OpenSSL S_TIME(1)
2
3
4
6 openssl-s_time, s_time - SSL/TLS performance timing program
7
9 openssl s_time [-help] [-connect host:port] [-www page] [-cert
10 filename] [-key filename] [-CApath directory] [-cafile filename]
11 [-no-CAfile] [-no-CApath] [-reuse] [-new] [-verify depth] [-nameopt
12 option] [-time seconds] [-ssl3] [-bugs] [-cipher cipherlist]
13 [-ciphersuites val]
14
16 The s_time command implements a generic SSL/TLS client which connects
17 to a remote host using SSL/TLS. It can request a page from the server
18 and includes the time to transfer the payload data in its timing
19 measurements. It measures the number of connections within a given
20 timeframe, the amount of data transferred (if any), and calculates the
21 average time spent for one connection.
22
24 -help
25 Print out a usage message.
26
27 -connect host:port
28 This specifies the host and optional port to connect to.
29
30 -www page
31 This specifies the page to GET from the server. A value of '/' gets
32 the index.htm[l] page. If this parameter is not specified, then
33 s_time will only perform the handshake to establish SSL connections
34 but not transfer any payload data.
35
36 -cert certname
37 The certificate to use, if one is requested by the server. The
38 default is not to use a certificate. The file is in PEM format.
39
40 -key keyfile
41 The private key to use. If not specified then the certificate file
42 will be used. The file is in PEM format.
43
44 -verify depth
45 The verify depth to use. This specifies the maximum length of the
46 server certificate chain and turns on server certificate
47 verification. Currently the verify operation continues after
48 errors so all the problems with a certificate chain can be seen. As
49 a side effect the connection will never fail due to a server
50 certificate verify failure.
51
52 -nameopt option
53 Option which determines how the subject or issuer names are
54 displayed. The option argument can be a single option or multiple
55 options separated by commas. Alternatively the -nameopt switch may
56 be used more than once to set multiple options. See the x509(1)
57 manual page for details.
58
59 -CApath directory
60 The directory to use for server certificate verification. This
61 directory must be in "hash format", see verify for more
62 information. These are also used when building the client
63 certificate chain.
64
65 -CAfile file
66 A file containing trusted certificates to use during server
67 authentication and to use when attempting to build the client
68 certificate chain.
69
70 -no-CAfile
71 Do not load the trusted CA certificates from the default file
72 location
73
74 -no-CApath
75 Do not load the trusted CA certificates from the default directory
76 location
77
78 -new
79 Performs the timing test using a new session ID for each
80 connection. If neither -new nor -reuse are specified, they are
81 both on by default and executed in sequence.
82
83 -reuse
84 Performs the timing test using the same session ID; this can be
85 used as a test that session caching is working. If neither -new nor
86 -reuse are specified, they are both on by default and executed in
87 sequence.
88
89 -ssl3
90 This option disables the use of SSL version 3. By default the
91 initial handshake uses a method which should be compatible with all
92 servers and permit them to use SSL v3 or TLS as appropriate.
93
94 The timing program is not as rich in options to turn protocols on
95 and off as the s_client(1) program and may not connect to all
96 servers. Unfortunately there are a lot of ancient and broken
97 servers in use which cannot handle this technique and will fail to
98 connect. Some servers only work if TLS is turned off with the -ssl3
99 option.
100
101 Note that this option may not be available, depending on how
102 OpenSSL was built.
103
104 -bugs
105 There are several known bug in SSL and TLS implementations. Adding
106 this option enables various workarounds.
107
108 -cipher cipherlist
109 This allows the TLSv1.2 and below cipher list sent by the client to
110 be modified. This list will be combined with any TLSv1.3
111 ciphersuites that have been configured. Although the server
112 determines which cipher suite is used it should take the first
113 supported cipher in the list sent by the client. See ciphers(1) for
114 more information.
115
116 -ciphersuites val
117 This allows the TLSv1.3 ciphersuites sent by the client to be
118 modified. This list will be combined with any TLSv1.2 and below
119 ciphersuites that have been configured. Although the server
120 determines which cipher suite is used it should take the first
121 supported cipher in the list sent by the client. See ciphers(1) for
122 more information. The format for this list is a simple colon (":")
123 separated list of TLSv1.3 ciphersuite names.
124
125 -time length
126 Specifies how long (in seconds) s_time should establish connections
127 and optionally transfer payload data from a server. Server and
128 client performance and the link speed determine how many
129 connections s_time can establish.
130
132 s_time can be used to measure the performance of an SSL connection. To
133 connect to an SSL HTTP server and get the default page the command
134
135 openssl s_time -connect servername:443 -www / -CApath yourdir -CAfile yourfile.pem -cipher commoncipher [-ssl3]
136
137 would typically be used (https uses port 443). 'commoncipher' is a
138 cipher to which both client and server can agree, see the ciphers(1)
139 command for details.
140
141 If the handshake fails then there are several possible causes, if it is
142 nothing obvious like no client certificate then the -bugs and -ssl3
143 options can be tried in case it is a buggy server. In particular you
144 should play with these options before submitting a bug report to an
145 OpenSSL mailing list.
146
147 A frequent problem when attempting to get client certificates working
148 is that a web client complains it has no certificates or gives an empty
149 list to choose from. This is normally because the server is not sending
150 the clients certificate authority in its "acceptable CA list" when it
151 requests a certificate. By using s_client(1) the CA list can be viewed
152 and checked. However some servers only request client authentication
153 after a specific URL is requested. To obtain the list in this case it
154 is necessary to use the -prexit option of s_client(1) and send an HTTP
155 request for an appropriate page.
156
157 If a certificate is specified on the command line using the -cert
158 option it will not be used unless the server specifically requests a
159 client certificate. Therefor merely including a client certificate on
160 the command line is no guarantee that the certificate works.
161
163 Because this program does not have all the options of the s_client(1)
164 program to turn protocols on and off, you may not be able to measure
165 the performance of all protocols with all servers.
166
167 The -verify option should really exit if the server verification fails.
168
170 s_client(1), s_server(1), ciphers(1)
171
173 Copyright 2004-2018 The OpenSSL Project Authors. All Rights Reserved.
174
175 Licensed under the OpenSSL license (the "License"). You may not use
176 this file except in compliance with the License. You can obtain a copy
177 in the file LICENSE in the source distribution or at
178 <https://www.openssl.org/source/license.html>.
179
180
181
1821.1.1 2018-09-11 S_TIME(1)