Seth Woolley's Man Viewer

s_time(1) - s_time - SSL/TLS performance timing program - man 1 s_time

([section] manual, -k keyword, -K [section] search, -f whatis)
man plain no title

S_TIME(1)                           OpenSSL                          S_TIME(1)

       s_time - SSL/TLS performance timing program

       openssl s_time [-connect host:port] [-www page] [-cert filename] [-key
       filename] [-CApath directory] [-CAfile filename] [-reuse] [-new] [-ver-
       ify depth] [-nbio] [-time seconds] [-ssl2] [-ssl3] [-bugs] [-cipher

       The s_client command implements a generic SSL/TLS client which connects
       to a remote host(1,5) using SSL/TLS. It can request a page from the server
       and includes the time(1,2,n) to transfer the payload data in(1,8) its timing mea-
       surements. It measures the number of connections within a given time-
       frame, the amount of data transferred (if(3,n) any), and calculates the
       average time(1,2,n) spent for one connection.

       -connect host:port
           This specifies the host(1,5) and optional port to connect to.

       -www page
           This specifies the page to GET from the server. A value of '/' gets(3,n)
           the index.htm[l] page. If this parameter is not specified, then
           s_time will only perform the handshake to establish SSL connections
           but not transfer any payload data.

       -cert certname
           The certificate to use, if(3,n) one is requested by the server. The
           default is not to use a certificate. The file(1,n) is in(1,8) PEM format.

       -key keyfile
           The private key to use. If not specified then the certificate file(1,n)
           will be used. The file(1,n) is in(1,8) PEM format.

       -verify depth
           The verify(1,8) depth to use. This specifies the maximum length of the
           server certificate chain and turns on server certificate verifica-
           tion.  Currently the verify(1,8) operation continues after errors so all
           the problems with a certificate chain can be seen. As a side effect
           the connection will never fail due to a server certificate verify(1,8)

       -CApath directory
           The directory to use for server certificate verification. This
           directory must be in(1,8) "hash format", see verify(1,8) for more informa-
           tion. These are also used when building the client certificate

       -CAfile file(1,n)
           A file(1,n) containing trusted certificates to use during server authen-
           tication and to use when attempting to build the client certificate

           performs the timing test using a new session ID for each connec-
           tion.  If neither -new nor -reuse are specified, they are both on
           by default and executed in(1,8) sequence.

           performs the timing test using the same session ID; this can be
           used as a test that session caching is working. If neither -new nor
           -reuse are specified, they are both on by default and executed in(1,8)

           turns on non-blocking I/O.

       -ssl2, -ssl3
           these options disable the use of certain SSL or TLS protocols. By
           default the initial handshake uses a method which should be compat-
           ible with all servers and permit them to use SSL v3, SSL v2 or TLS
           as appropriate.  The timing program is not as rich in(1,8) options to
           turn protocols on and off as the s_client(1) program and may not
           connect to all servers.

           Unfortunately there are a lot of ancient and broken servers in(1,8) use
           which cannot handle this technique and will fail to connect. Some
           servers only work if(3,n) TLS is turned off with the -ssl3 option; oth-
           ers will only support SSL v2 and may need the -ssl2 option.

           there are several known bug in(1,8) SSL and TLS implementations. Adding
           this option enables various workarounds.

       -cipher cipherlist
           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(1,8) the list sent by the client.
           See the ciphers(1) command for more information.

       -time length
           specifies how long (in(1,8) seconds) s_time should establish connections
           and optionally transfer payload data from a server. Server and
           client performance and the link(1,2) speed determine how many connec-
           tions s_time can establish.

       s_client can be used to measure the performance of an SSL connection.
       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 ciphers(1)
       command for details.

       If the handshake fails then there are several possible causes, if(3,n) it is
       nothing obvious like no client certificate then the -bugs, -ssl2, -ssl3
       options can be tried in(1,8) case it is a buggy server. In particular you
       should play with these options before submitting a bug report to an
       OpenSSL mailing list.

       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(1,8) its "acceptable CA list" when it
       requests a certificate. By using 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(1,8) this case it
       is necessary to use the -prexit option of s_client(1) and send(2,n) an HTTP
       request for an appropriate page.

       If a certificate is specified on the command line using the -cert
       option it will not be used unless the server specifically requests a
       client certificate. Therefor merely including a client certificate on
       the command line is no guarantee that the certificate works.

       Because this program does not have all the options of the 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 -verify option should really exit(3,n,1 builtins) if(3,n) the server verification fails.

       s_client(1), s_server(1), ciphers(1)

0.9.7d                            2004-01-07                         S_TIME(1)

References for this manual (incoming links)