Admin Control Panel v2.0

✎ Editing: s_client.html ← Back

<?xml version="1.0" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>s_client</title>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<link rev="made" href="mailto:root@localhost" />
</head>

<ul id="index">
 <li><a href="#NAME">NAME</a></li>
 <li><a href="#SYNOPSIS">SYNOPSIS</a></li>
 <li><a href="#DESCRIPTION">DESCRIPTION</a></li>
 <li><a href="#OPTIONS">OPTIONS</a></li>
 <li><a href="#CONNECTED-COMMANDS">CONNECTED COMMANDS</a></li>
 <li><a href="#NOTES">NOTES</a></li>
 <li><a href="#BUGS">BUGS</a></li>
 <li><a href="#SEE-ALSO">SEE ALSO</a></li>
 <li><a href="#HISTORY">HISTORY</a></li>
 <li><a href="#COPYRIGHT">COPYRIGHT</a></li>
</ul>

openssl-s_client, s_client - SSL/TLS client program

<h1 id="SYNOPSIS">SYNOPSIS</h1>

openssl s_client [-help] [-connect host:port] [-bind host:port] [-proxy host:port] [-unix path] [-4] [-6] [-servername name] [-noservername] [-verify depth] [-verify_return_error] [-cert filename] [-certform DER|PEM] [-key filename] [-keyform DER|PEM] [-cert_chain filename] [-build_chain] [-xkey] [-xcert] [-xchain] [-xchain_build] [-xcertform PEM|DER] [-xkeyform PEM|DER] [-pass arg] [-CApath directory] [-CAfile filename] [-chainCApath directory] [-chainCAfile filename] [-no-CAfile] [-no-CApath] [-requestCAfile filename] [-dane_tlsa_domain domain] [-dane_tlsa_rrdata rrdata] [-dane_ee_no_namechecks] [-attime timestamp] [-check_ss_sig] [-crl_check] [-crl_check_all] [-explicit_policy] [-extended_crl] [-ignore_critical] [-inhibit_any] [-inhibit_map] [-no_check_time] [-partial_chain] [-policy arg] [-policy_check] [-policy_print] [-purpose purpose] [-suiteB_128] [-suiteB_128_only] [-suiteB_192] [-trusted_first] [-no_alt_chains] [-use_deltas] [-auth_level num] [-nameopt option] [-verify_depth num] [-verify_email email] [-verify_hostname hostname] [-verify_ip ip] [-verify_name name] [-build_chain] [-x509_strict] [-reconnect] [-showcerts] [-debug] [-msg] [-nbio_test] [-state] [-nbio] [-crlf] [-ign_eof] [-no_ign_eof] [-psk_identity identity] [-psk key] [-psk_session file] [-quiet] [-ssl3] [-tls1] [-tls1_1] [-tls1_2] [-tls1_3] [-no_ssl3] [-no_tls1] [-no_tls1_1] [-no_tls1_2] [-no_tls1_3] [-dtls] [-dtls1] [-dtls1_2] [-sctp] [-sctp_label_bug] [-fallback_scsv] [-async] [-max_send_frag] [-split_send_frag] [-max_pipelines] [-read_buf] [-bugs] [-comp] [-no_comp] [-allow_no_dhe_kex] [-sigalgs sigalglist] [-curves curvelist] [-cipher cipherlist] [-ciphersuites val] [-serverpref] [-starttls protocol] [-xmpphost hostname] [-name hostname] [-engine id] [-tlsextdebug] [-no_ticket] [-sess_out filename] [-sess_in filename] [-rand file...] [-writerand file] [-serverinfo types] [-status] [-alpn protocols] [-nextprotoneg protocols] [-ct] [-noct] [-ctlogfile] [-keylogfile file] [-early_data file] [-enable_pha] [target]

<h1 id="DESCRIPTION">DESCRIPTION</h1>

The s_client command implements a generic SSL/TLS client which connects to a remote host using SSL/TLS. It is a very useful diagnostic tool for SSL servers.

<h1 id="OPTIONS">OPTIONS</h1>

In addition to the options below the s_client utility also supports the common and client only options documented in the &quot;Supported Command Line Commands&quot; section of the <a href="../man3/SSL_CONF_cmd.html">SSL_CONF_cmd(3)</a> manual page.

<dl>

Print out a usage message.

</dd>
<dt id="connect-host:port">-connect host:port</dt>
<dd>

This specifies the host and optional port to connect to. It is possible to select the host and port using the optional target positional argument instead. If neither this nor the target positional argument are specified then an attempt is made to connect to the local host on port 4433.

</dd>
<dt id="bind-host:port">-bind host:port]</dt>
<dd>

This specifies the host address and or port to bind as the source for the connection. For Unix-domain sockets the port is ignored and the host is used as the source socket address.

</dd>
<dt id="proxy-host:port">-proxy host:port</dt>
<dd>

When used with the -connect flag, the program uses the host and port specified with this flag and issues an HTTP CONNECT command to connect to the desired server.

</dd>
<dt id="unix-path">-unix path</dt>
<dd>

Connect over the specified Unix-domain socket.

</dd>
<dt id="pod-4">-4</dt>
<dd>

Use IPv4 only.

</dd>
<dt id="pod-6">-6</dt>
<dd>

Use IPv6 only.

</dd>
<dt id="servername-name">-servername name</dt>
<dd>

Set the TLS SNI (Server Name Indication) extension in the ClientHello message to the given value. If -servername is not provided, the TLS SNI extension will be populated with the name given to -connect if it follows a DNS name format. If -connect is not provided either, the SNI is set to &quot;localhost&quot;. This is the default since OpenSSL 1.1.1.

Even though SNI should normally be a DNS name and not an IP address, if -servername is provided then that name will be sent, regardless of whether it is a DNS name or not.

This option cannot be used in conjunction with -noservername.

</dd>
<dt id="noservername">-noservername</dt>
<dd>

Suppresses sending of the SNI (Server Name Indication) extension in the ClientHello message. Cannot be used in conjunction with the -servername or &lt;-dane_tlsa_domain&gt; options.

</dd>
<dt id="cert-certname">-cert certname</dt>
<dd>

The certificate to use, if one is requested by the server. The default is not to use a certificate.

</dd>
<dt id="certform-format">-certform format</dt>
<dd>

The certificate format to use: DER or PEM. PEM is the default.

</dd>
<dt id="key-keyfile">-key keyfile</dt>
<dd>

The private key to use. If not specified then the certificate file will be used.

</dd>
<dt id="keyform-format">-keyform format</dt>
<dd>

The private format to use: DER or PEM. PEM is the default.

</dd>
<dt id="cert_chain">-cert_chain</dt>
<dd>

A file containing trusted certificates to use when attempting to build the client/server certificate chain related to the certificate specified via the -cert option.

</dd>
<dt id="build_chain">-build_chain</dt>
<dd>

Specify whether the application should build the certificate chain to be provided to the server.

</dd>
<dt id="xkey-infile--xcert-infile--xchain">-xkey infile, -xcert infile, -xchain</dt>
<dd>

Specify an extra certificate, private key and certificate chain. These behave in the same manner as the -cert, -key and -cert_chain options. When specified, the callback returning the first valid chain will be in use by the client.

</dd>
<dt id="xchain_build">-xchain_build</dt>
<dd>

Specify whether the application should build the certificate chain to be provided to the server for the extra certificates provided via -xkey infile, -xcert infile, -xchain options.

</dd>
<dt id="xcertform-PEM-DER--xkeyform-PEM-DER">-xcertform PEM|DER, -xkeyform PEM|DER</dt>
<dd>

Extra certificate and private key format respectively.

</dd>
<dt id="pass-arg">-pass arg</dt>
<dd>

the private key password source. For more information about the format of arg see <a href="../man1/openssl.html">&quot;Pass Phrase Options&quot; in openssl(1)</a>.

</dd>
<dt id="verify-depth">-verify depth</dt>
<dd>

The verify depth to use. This specifies the maximum length of the server certificate chain and turns on server certificate verification. Currently the verify 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 failure.

</dd>
<dt id="verify_return_error">-verify_return_error</dt>
<dd>

Return verification errors instead of continuing. This will typically abort the handshake with a fatal error.

</dd>
<dt id="nameopt-option">-nameopt option</dt>
<dd>

Option which determines how the subject or issuer names are displayed. The option argument can be a single option or multiple options separated by commas. Alternatively the -nameopt switch may be used more than once to set multiple options. See the <a href="../man1/x509.html">x509(1)</a> manual page for details.

</dd>
<dt id="CApath-directory">-CApath directory</dt>
<dd>

The directory to use for server certificate verification. This directory must be in &quot;hash format&quot;, see <a href="../man1/verify.html">verify(1)</a> for more information. These are also used when building the client certificate chain.

</dd>
<dt id="CAfile-file">-CAfile file</dt>
<dd>

A file containing trusted certificates to use during server authentication and to use when attempting to build the client certificate chain.

</dd>
<dt id="chainCApath-directory">-chainCApath directory</dt>
<dd>

The directory to use for building the chain provided to the server. This directory must be in &quot;hash format&quot;, see <a href="../man1/verify.html">verify(1)</a> for more information.

</dd>
<dt id="chainCAfile-file">-chainCAfile file</dt>
<dd>

A file containing trusted certificates to use when attempting to build the client certificate chain.

</dd>
<dt id="no-CAfile">-no-CAfile</dt>
<dd>

Do not load the trusted CA certificates from the default file location

</dd>
<dt id="no-CApath">-no-CApath</dt>
<dd>

Do not load the trusted CA certificates from the default directory location

</dd>
<dt id="requestCAfile-file">-requestCAfile file</dt>
<dd>

A file containing a list of certificates whose subject names will be sent to the server in the certificate_authorities extension. Only supported for TLS 1.3

</dd>
<dt id="dane_tlsa_domain-domain">-dane_tlsa_domain domain</dt>
<dd>

Enable RFC6698/RFC7671 DANE TLSA authentication and specify the TLSA base domain which becomes the default SNI hint and the primary reference identifier for hostname checks. This must be used in combination with at least one instance of the -dane_tlsa_rrdata option below.

When DANE authentication succeeds, the diagnostic output will include the lowest (closest to 0) depth at which a TLSA record authenticated a chain certificate. When that TLSA record is a &quot;2 1 0&quot; trust anchor public key that signed (rather than matched) the top-most certificate of the chain, the result is reported as &quot;TA public key verified&quot;. Otherwise, either the TLSA record &quot;matched TA certificate&quot; at a positive depth or else &quot;matched EE certificate&quot; at depth 0.

</dd>
<dt id="dane_tlsa_rrdata-rrdata">-dane_tlsa_rrdata rrdata</dt>
<dd>

Use one or more times to specify the RRDATA fields of the DANE TLSA RRset associated with the target service. The rrdata value is specified in &quot;presentation form&quot;, that is four whitespace separated fields that specify the usage, selector, matching type and associated data, with the last of these encoded in hexadecimal. Optional whitespace is ignored in the associated data field. For example:

<pre><code> $ openssl s_client -brief -starttls smtp \
 -connect smtp.example.com:25 \
 -dane_tlsa_domain smtp.example.com \
 -dane_tlsa_rrdata &quot;2 1 1
 B111DD8A1C2091A89BD4FD60C57F0716CCE50FEEFF8137CDBEE0326E 02CF362B&quot; \
 -dane_tlsa_rrdata &quot;2 1 1
 60B87575447DCBA2A36B7D11AC09FB24A9DB406FEE12D2CC90180517 616E8A18&quot;
 ...
 Verification: OK
 Verified peername: smtp.example.com
 DANE TLSA 2 1 1 ...ee12d2cc90180517616e8a18 matched TA certificate at depth 1
 ...</code></pre>

</dd>
<dt id="dane_ee_no_namechecks">-dane_ee_no_namechecks</dt>
<dd>

This disables server name checks when authenticating via DANE-EE(3) TLSA records. For some applications, primarily web browsers, it is not safe to disable name checks due to &quot;unknown key share&quot; attacks, in which a malicious server can convince a client that a connection to a victim server is instead a secure connection to the malicious server. The malicious server may then be able to violate cross-origin scripting restrictions. Thus, despite the text of RFC7671, name checks are by default enabled for DANE-EE(3) TLSA records, and can be disabled in applications where it is safe to do so. In particular, SMTP and XMPP clients should set this option as SRV and MX records already make it possible for a remote domain to redirect client connections to any server of its choice, and in any case SMTP and XMPP clients do not execute scripts downloaded from remote servers.

</dd>
<dt id="attime--check_ss_sig--crl_check--crl_check_all--explicit_policy--extended_crl--ignore_critical--inhibit_any--inhibit_map--no_alt_chains--no_check_time--partial_chain--policy--policy_check--policy_print--purpose--suiteB_128--suiteB_128_only--suiteB_192--trusted_first--use_deltas--auth_level--verify_depth--verify_email--verify_hostname--verify_ip--verify_name--x509_strict">-attime, -check_ss_sig, -crl_check, -crl_check_all, -explicit_policy, -extended_crl, -ignore_critical, -inhibit_any, -inhibit_map, -no_alt_chains, -no_check_time, -partial_chain, -policy, -policy_check, -policy_print, -purpose, -suiteB_128, -suiteB_128_only, -suiteB_192, -trusted_first, -use_deltas, -auth_level, -verify_depth, -verify_email, -verify_hostname, -verify_ip, -verify_name, -x509_strict</dt>
<dd>

Set various certificate chain validation options. See the <a href="../man1/verify.html">verify(1)</a> manual page for details.

</dd>
<dt id="reconnect">-reconnect</dt>
<dd>

Reconnects to the same server 5 times using the same session ID, this can be used as a test that session caching is working.

</dd>
<dt id="showcerts">-showcerts</dt>
<dd>

Displays the server certificate list as sent by the server: it only consists of certificates the server has sent (in the order the server has sent them). It is not a verified chain.

</dd>
<dt id="prexit">-prexit</dt>
<dd>

Print session information when the program exits. This will always attempt to print out information even if the connection fails. Normally information will only be printed out once if the connection succeeds. This option is useful because the cipher in use may be renegotiated or the connection may fail because a client certificate is required or is requested only after an attempt is made to access a certain URL. Note: the output produced by this option is not always accurate because a connection might never have been established.

</dd>
<dt id="state">-state</dt>
<dd>

Prints out the SSL session states.

</dd>
<dt id="debug">-debug</dt>
<dd>

Print extensive debugging information including a hex dump of all traffic.

</dd>
<dt id="msg">-msg</dt>
<dd>

Show all protocol messages with hex dump.

</dd>
<dt id="trace">-trace</dt>
<dd>

Show verbose trace output of protocol messages. OpenSSL needs to be compiled with enable-ssl-trace for this option to work.

</dd>
<dt id="msgfile">-msgfile</dt>
<dd>

File to send output of -msg or -trace to, default standard output.

</dd>
<dt id="nbio_test">-nbio_test</dt>
<dd>

Tests nonblocking I/O

</dd>
<dt id="nbio">-nbio</dt>
<dd>

Turns on nonblocking I/O

</dd>
<dt id="crlf">-crlf</dt>
<dd>

This option translated a line feed from the terminal into CR+LF as required by some servers.

</dd>
<dt id="ign_eof">-ign_eof</dt>
<dd>

Inhibit shutting down the connection when end of file is reached in the input.

</dd>
<dt id="quiet">-quiet</dt>
<dd>

Inhibit printing of session and certificate information. This implicitly turns on -ign_eof as well.

</dd>
<dt id="no_ign_eof">-no_ign_eof</dt>
<dd>

Shut down the connection when end of file is reached in the input. Can be used to override the implicit -ign_eof after -quiet.

</dd>
<dt id="psk_identity-identity">-psk_identity identity</dt>
<dd>

Use the PSK identity identity when using a PSK cipher suite. The default value is &quot;Client_identity&quot; (without the quotes).

</dd>
<dt id="psk-key">-psk key</dt>
<dd>

Use the PSK key key when using a PSK cipher suite. The key is given as a hexadecimal number without leading 0x, for example -psk 1a2b3c4d. This option must be provided in order to use a PSK cipher.

</dd>
<dt id="psk_session-file">-psk_session file</dt>
<dd>

Use the pem encoded SSL_SESSION data stored in file as the basis of a PSK. Note that this will only work if TLSv1.3 is negotiated.

</dd>
<dt id="ssl3--tls1--tls1_1--tls1_2--tls1_3--no_ssl3--no_tls1--no_tls1_1--no_tls1_2--no_tls1_3">-ssl3, -tls1, -tls1_1, -tls1_2, -tls1_3, -no_ssl3, -no_tls1, -no_tls1_1, -no_tls1_2, -no_tls1_3</dt>
<dd>

These options require or disable the use of the specified SSL or TLS protocols. By default s_client will negotiate the highest mutually supported protocol version. When a specific TLS version is required, only that version will be offered to and accepted from the server. Note that not all protocols and flags may be available, depending on how OpenSSL was built.

</dd>
<dt id="dtls--dtls1--dtls1_2">-dtls, -dtls1, -dtls1_2</dt>
<dd>

These options make s_client use DTLS protocols instead of TLS. With -dtls, s_client will negotiate any supported DTLS protocol version, whilst -dtls1 and -dtls1_2 will only support DTLS1.0 and DTLS1.2 respectively.

</dd>
<dt id="sctp">-sctp</dt>
<dd>

Use SCTP for the transport protocol instead of UDP in DTLS. Must be used in conjunction with -dtls, -dtls1 or -dtls1_2. This option is only available where OpenSSL has support for SCTP enabled.

</dd>
<dt id="sctp_label_bug">-sctp_label_bug</dt>
<dd>

Use the incorrect behaviour of older OpenSSL implementations when computing endpoint-pair shared secrets for DTLS/SCTP. This allows communication with older broken implementations but breaks interoperability with correct implementations. Must be used in conjunction with -sctp. This option is only available where OpenSSL has support for SCTP enabled.

</dd>
<dt id="fallback_scsv">-fallback_scsv</dt>
<dd>

Send TLS_FALLBACK_SCSV in the ClientHello.

</dd>
<dt id="async">-async</dt>
<dd>

Switch on asynchronous mode. Cryptographic operations will be performed asynchronously. This will only have an effect if an asynchronous capable engine is also used via the -engine option. For test purposes the dummy async engine (dasync) can be used (if available).

</dd>
<dt id="max_send_frag-int">-max_send_frag int</dt>
<dd>

The maximum size of data fragment to send. See <a href="../man3/SSL_CTX_set_max_send_fragment.html">SSL_CTX_set_max_send_fragment(3)</a> for further information.

</dd>
<dt id="split_send_frag-int">-split_send_frag int</dt>
<dd>

The size used to split data for encrypt pipelines. If more data is written in one go than this value then it will be split into multiple pipelines, up to the maximum number of pipelines defined by max_pipelines. This only has an effect if a suitable cipher suite has been negotiated, an engine that supports pipelining has been loaded, and max_pipelines is greater than 1. See <a href="../man3/SSL_CTX_set_split_send_fragment.html">SSL_CTX_set_split_send_fragment(3)</a> for further information.

</dd>
<dt id="max_pipelines-int">-max_pipelines int</dt>
<dd>

The maximum number of encrypt/decrypt pipelines to be used. This will only have an effect if an engine has been loaded that supports pipelining (e.g. the dasync engine) and a suitable cipher suite has been negotiated. The default value is 1. See <a href="../man3/SSL_CTX_set_max_pipelines.html">SSL_CTX_set_max_pipelines(3)</a> for further information.

</dd>
<dt id="read_buf-int">-read_buf int</dt>
<dd>

The default read buffer size to be used for connections. This will only have an effect if the buffer size is larger than the size that would otherwise be used and pipelining is in use (see <a href="../man3/SSL_CTX_set_default_read_buffer_len.html">SSL_CTX_set_default_read_buffer_len(3)</a> for further information).

</dd>
<dt id="bugs">-bugs</dt>
<dd>

There are several known bugs in SSL and TLS implementations. Adding this option enables various workarounds.

</dd>
<dt id="comp">-comp</dt>
<dd>

Enables support for SSL/TLS compression. This option was introduced in OpenSSL 1.1.0. TLS compression is not recommended and is off by default as of OpenSSL 1.1.0.

</dd>
<dt id="no_comp">-no_comp</dt>
<dd>

Disables support for SSL/TLS compression. TLS compression is not recommended and is off by default as of OpenSSL 1.1.0.

</dd>
<dt id="brief">-brief</dt>
<dd>

Only provide a brief summary of connection parameters instead of the normal verbose output.

</dd>
<dt id="sigalgs-sigalglist">-sigalgs sigalglist</dt>
<dd>

Specifies the list of signature algorithms that are sent by the client. The server selects one entry in the list based on its preferences. For example strings, see <a href="../man3/SSL_CTX_set1_sigalgs.html">SSL_CTX_set1_sigalgs(3)</a>

</dd>
<dt id="curves-curvelist">-curves curvelist</dt>
<dd>

Specifies the list of supported curves to be sent by the client. The curve is ultimately selected by the server. For a list of all curves, use:

<pre><code> $ openssl ecparam -list_curves</code></pre>

</dd>
<dt id="cipher-cipherlist">-cipher cipherlist</dt>
<dd>

This allows the TLSv1.2 and below cipher list sent by the client to be modified. This list will be combined with any TLSv1.3 ciphersuites that have been configured. Although the server determines which ciphersuite is used it should take the first supported cipher in the list sent by the client. See the ciphers command for more information.

</dd>
<dt id="ciphersuites-val">-ciphersuites val</dt>
<dd>

This allows the TLSv1.3 ciphersuites sent by the client to be modified. This list will be combined with any TLSv1.2 and below ciphersuites that have been configured. 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 ciphers command for more information. The format for this list is a simple colon (&quot;:&quot;) separated list of TLSv1.3 ciphersuite names.

</dd>
<dt id="starttls-protocol">-starttls protocol</dt>
<dd>

Send the protocol-specific message(s) to switch to TLS for communication. protocol is a keyword for the intended protocol. Currently, the only supported keywords are &quot;smtp&quot;, &quot;pop3&quot;, &quot;imap&quot;, &quot;ftp&quot;, &quot;xmpp&quot;, &quot;xmpp-server&quot;, &quot;irc&quot;, &quot;postgres&quot;, &quot;mysql&quot;, &quot;lmtp&quot;, &quot;nntp&quot;, &quot;sieve&quot; and &quot;ldap&quot;.

</dd>
<dt id="xmpphost-hostname">-xmpphost hostname</dt>
<dd>

This option, when used with &quot;-starttls xmpp&quot; or &quot;-starttls xmpp-server&quot;, specifies the host for the &quot;to&quot; attribute of the stream element. If this option is not specified, then the host specified with &quot;-connect&quot; will be used.

This option is an alias of the -name option for &quot;xmpp&quot; and &quot;xmpp-server&quot;.

</dd>
<dt id="name-hostname">-name hostname</dt>
<dd>

This option is used to specify hostname information for various protocols used with -starttls option. Currently only &quot;xmpp&quot;, &quot;xmpp-server&quot;, &quot;smtp&quot; and &quot;lmtp&quot; can utilize this -name option.

If this option is used with &quot;-starttls xmpp&quot; or &quot;-starttls xmpp-server&quot;, if specifies the host for the &quot;to&quot; attribute of the stream element. If this option is not specified, then the host specified with &quot;-connect&quot; will be used.

If this option is used with &quot;-starttls lmtp&quot; or &quot;-starttls smtp&quot;, it specifies the name to use in the &quot;LMTP LHLO&quot; or &quot;SMTP EHLO&quot; message, respectively. If this option is not specified, then &quot;mail.example.com&quot; will be used.

</dd>
<dt id="tlsextdebug">-tlsextdebug</dt>
<dd>

Print out a hex dump of any TLS extensions received from the server.

</dd>
<dt id="no_ticket">-no_ticket</dt>
<dd>

Disable RFC4507bis session ticket support.

</dd>
<dt id="sess_out-filename">-sess_out filename</dt>
<dd>

Output SSL session to filename.

</dd>
<dt id="sess_in-sess.pem">-sess_in sess.pem</dt>
<dd>

Load SSL session from filename. The client will attempt to resume a connection from this session.

</dd>
<dt id="engine-id">-engine id</dt>
<dd>

Specifying an engine (by its unique id string) will cause s_client to attempt to obtain a functional reference to the specified engine, thus initialising it if needed. The engine will then be set as the default for all available algorithms.

</dd>
<dt id="rand-file">-rand file...</dt>
<dd>

A file or files containing random data used to seed the random number generator. Multiple files can be specified separated by an OS-dependent character. The separator is ; for MS-Windows, , for OpenVMS, and : for all others.

</dd>
<dt id="writerand-file">[-writerand file]</dt>
<dd>

Writes random data to the specified file upon exit. This can be used with a subsequent -rand flag.

</dd>
<dt id="serverinfo-types">-serverinfo types</dt>
<dd>

A list of comma-separated TLS Extension Types (numbers between 0 and 65535). Each type will be sent as an empty ClientHello TLS Extension. The server&#39;s response (if any) will be encoded and displayed as a PEM file.

</dd>
<dt id="status">-status</dt>
<dd>

Sends a certificate status request to the server (OCSP stapling). The server response (if any) is printed out.

</dd>
<dt id="alpn-protocols--nextprotoneg-protocols">-alpn protocols, -nextprotoneg protocols</dt>
<dd>

These flags enable the Enable the Application-Layer Protocol Negotiation or Next Protocol Negotiation (NPN) extension, respectively. ALPN is the IETF standard and replaces NPN. The protocols list is a comma-separated list of protocol names that the client should advertise support for. The list should contain the most desirable protocols first. Protocol names are printable ASCII strings, for example &quot;http/1.1&quot; or &quot;spdy/3&quot;. An empty list of protocols is treated specially and will cause the client to advertise support for the TLS extension but disconnect just after receiving ServerHello with a list of server supported protocols. The flag -nextprotoneg cannot be specified if -tls1_3 is used.

</dd>
<dt id="ct--noct">-ct, -noct</dt>
<dd>

Use one of these two options to control whether Certificate Transparency (CT) is enabled (-ct) or disabled (-noct). If CT is enabled, signed certificate timestamps (SCTs) will be requested from the server and reported at handshake completion.

Enabling CT also enables OCSP stapling, as this is one possible delivery method for SCTs.

</dd>
<dt id="ctlogfile">-ctlogfile</dt>
<dd>

A file containing a list of known Certificate Transparency logs. See <a href="../man3/SSL_CTX_set_ctlog_list_file.html">SSL_CTX_set_ctlog_list_file(3)</a> for the expected file format.

</dd>
<dt id="keylogfile-file">-keylogfile file</dt>
<dd>

Appends TLS secrets to the specified keylog file such that external programs (like Wireshark) can decrypt TLS connections.

</dd>
<dt id="early_data-file">-early_data file</dt>
<dd>

Reads the contents of the specified file and attempts to send it as early data to the server. This will only work with resumed sessions that support early data and when the server accepts the early data.

</dd>
<dt id="enable_pha">-enable_pha</dt>
<dd>

For TLSv1.3 only, send the Post-Handshake Authentication extension. This will happen whether or not a certificate has been provided via -cert.

</dd>
<dt id="target">[target]</dt>
<dd>

Rather than providing -connect, the target hostname and optional port may be provided as a single positional argument after all options. If neither this nor -connect are provided, falls back to attempting to connect to localhost on port 4433.

</dd>
</dl>

<h1 id="CONNECTED-COMMANDS">CONNECTED COMMANDS</h1>

If a connection is established with an SSL server then any data received from the server is displayed and any key presses will be sent to the server. If end of file is reached then the connection will be closed down. When used interactively (which means neither -quiet nor -ign_eof have been given), then certain commands are also recognized which perform special operations. These commands are a letter which must appear at the start of a line. They are listed below.

<dl>

End the current SSL connection and exit.

</dd>
<dt id="R">R</dt>
<dd>

Renegotiate the SSL session (TLSv1.2 and below only).

</dd>
<dt id="B">B</dt>
<dd>

Send a heartbeat message to the server (DTLS only)

</dd>
<dt id="k">k</dt>
<dd>

Send a key update message to the server (TLSv1.3 only)

</dd>
<dt id="K">K</dt>
<dd>

Send a key update message to the server and request one back (TLSv1.3 only)

</dd>
</dl>

<h1 id="NOTES">NOTES</h1>

s_client can be used to debug SSL servers. To connect to an SSL HTTP server the command:

<pre><code> openssl s_client -connect servername:443</code></pre>

would typically be used (https uses port 443). If the connection succeeds then an HTTP command can be given such as &quot;GET /&quot; to retrieve a web page.

If the handshake fails then there are several possible causes, if it is nothing obvious like no client certificate then the -bugs, -ssl3, -tls1, -no_ssl3, -no_tls1 options can be tried in 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 its &quot;acceptable CA list&quot; when it requests a certificate. By using s_client 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 -prexit option and send 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. Therefore, merely including a client certificate on the command line is no guarantee that the certificate works.

If there are problems verifying a server certificate then the -showcerts option can be used to show all the certificates sent by the server.

The s_client utility is a test tool and is designed to continue the handshake after any certificate verification errors. As a result it will accept any certificate chain (trusted or not) sent by the peer. Non-test applications should not do this as it makes them vulnerable to a MITM attack. This behaviour can be changed by with the -verify_return_error option: any verify errors are then returned aborting the handshake.

The -bind option may be useful if the server or a firewall requires connections to come from some particular address and or port.

Because this program has a lot of options and also because some of the techniques used are rather old, the C source of s_client is rather hard to read and not a model of how things should be done. A typical SSL client program would be much simpler.

The -prexit option is a bit of a hack. We should really report information whenever a session is renegotiated.

<a href="../man3/SSL_CONF_cmd.html">SSL_CONF_cmd(3)</a>, <a href="../man1/sess_id.html">sess_id(1)</a>, <a href="../man1/s_server.html">s_server(1)</a>, <a href="../man1/ciphers.html">ciphers(1)</a>, <a href="../man3/SSL_CTX_set_max_send_fragment.html">SSL_CTX_set_max_send_fragment(3)</a>, <a href="../man3/SSL_CTX_set_split_send_fragment.html">SSL_CTX_set_split_send_fragment(3)</a>, <a href="../man3/SSL_CTX_set_max_pipelines.html">SSL_CTX_set_max_pipelines(3)</a>

<h1 id="HISTORY">HISTORY</h1>

The -no_alt_chains option was added in OpenSSL 1.1.0. The -name option was added in OpenSSL 1.1.1.

<h1 id="COPYRIGHT">COPYRIGHT</h1>

Licensed under the OpenSSL license (the &quot;License&quot;). You may not use this file except in compliance with the License. You can obtain a copy in the file LICENSE in the source distribution or at <a href="https://www.openssl.org/source/license.html">https://www.openssl.org/source/license.html</a>.

</body>

</html>

Cancel