Admin Control Panel v2.0

✎ Editing: s_server.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_server</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_server, s_server - SSL/TLS server program

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

openssl s_server [-help] [-port +int] [-accept val] [-unix val] [-4] [-6] [-unlink] [-context val] [-verify int] [-Verify int] [-cert infile] [-nameopt val] [-naccept +int] [-serverinfo val] [-certform PEM|DER] [-key infile] [-keyform format] [-pass val] [-dcert infile] [-dcertform PEM|DER] [-dkey infile] [-dkeyform PEM|DER] [-dpass val] [-nbio_test] [-crlf] [-debug] [-msg] [-msgfile outfile] [-state] [-CAfile infile] [-CApath dir] [-no-CAfile] [-no-CApath] [-nocert] [-quiet] [-no_resume_ephemeral] [-www] [-WWW] [-servername] [-servername_fatal] [-cert2 infile] [-key2 infile] [-tlsextdebug] [-HTTP] [-id_prefix val] [-rand file...] [-writerand file] [-keymatexport val] [-keymatexportlen +int] [-CRL infile] [-crl_download] [-cert_chain infile] [-dcert_chain infile] [-chainCApath dir] [-verifyCApath dir] [-no_cache] [-ext_cache] [-CRLform PEM|DER] [-verify_return_error] [-verify_quiet] [-build_chain] [-chainCAfile infile] [-verifyCAfile infile] [-ign_eof] [-no_ign_eof] [-status] [-status_verbose] [-status_timeout int] [-status_url val] [-status_file infile] [-trace] [-security_debug] [-security_debug_verbose] [-brief] [-rev] [-async] [-ssl_config val] [-max_send_frag +int] [-split_send_frag +int] [-max_pipelines +int] [-read_buf +int] [-no_ssl3] [-no_tls1] [-no_tls1_1] [-no_tls1_2] [-no_tls1_3] [-bugs] [-no_comp] [-comp] [-no_ticket] [-num_tickets] [-serverpref] [-legacy_renegotiation] [-no_renegotiation] [-legacy_server_connect] [-no_resumption_on_reneg] [-no_legacy_server_connect] [-allow_no_dhe_kex] [-prioritize_chacha] [-strict] [-sigalgs val] [-client_sigalgs val] [-groups val] [-curves val] [-named_curve val] [-cipher val] [-ciphersuites val] [-dhparam infile] [-record_padding val] [-debug_broken_protocol] [-policy val] [-purpose val] [-verify_name val] [-verify_depth int] [-auth_level int] [-attime intmax] [-verify_hostname val] [-verify_email val] [-verify_ip] [-ignore_critical] [-issuer_checks] [-crl_check] [-crl_check_all] [-policy_check] [-explicit_policy] [-inhibit_any] [-inhibit_map] [-x509_strict] [-extended_crl] [-use_deltas] [-policy_print] [-check_ss_sig] [-trusted_first] [-suiteB_128_only] [-suiteB_128] [-suiteB_192] [-partial_chain] [-no_alt_chains] [-no_check_time] [-allow_proxy_certs] [-xkey] [-xcert] [-xchain] [-xchain_build] [-xcertform PEM|DER] [-xkeyform PEM|DER] [-nbio] [-psk_identity val] [-psk_hint val] [-psk val] [-psk_session file] [-srpvfile infile] [-srpuserseed val] [-ssl3] [-tls1] [-tls1_1] [-tls1_2] [-tls1_3] [-dtls] [-timeout] [-mtu +int] [-listen] [-dtls1] [-dtls1_2] [-sctp] [-sctp_label_bug] [-no_dhe] [-nextprotoneg val] [-use_srtp val] [-alpn val] [-engine val] [-keylogfile outfile] [-max_early_data int] [-early_data] [-anti_replay] [-no_anti_replay]

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

The s_server command implements a generic SSL/TLS server which listens for connections on a given port using SSL/TLS.

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

In addition to the options below the s_server utility also supports the common and server 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="port-int">-port +int</dt>
<dd>

The TCP port to listen on for connections. If not specified 4433 is used.

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

The optional TCP host and port to listen on for connections. If not specified, *:4433 is used.

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

Unix domain socket to accept on.

</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="unlink">-unlink</dt>
<dd>

For -unix, unlink any existing socket first.

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

Sets the SSL context id. It can be given any string value. If this option is not present a default value will be used.

</dd>
<dt id="verify-int--Verify-int">-verify int, -Verify int</dt>
<dd>

The verify depth to use. This specifies the maximum length of the client certificate chain and makes the server request a certificate from the client. With the -verify option a certificate is requested but the client does not have to send one, with the -Verify option the client must supply a certificate or an error occurs.

If the cipher suite cannot request a client certificate (for example an anonymous cipher suite or PSK) this option has no effect.

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

The certificate to use, most servers cipher suites require the use of a certificate and some require a certificate with a certain public key type: for example the DSS cipher suites require a certificate containing a DSS (DSA) key. If not specified then the filename &quot;server.pem&quot; will be used.

</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 client.

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

Option which determines how the subject or issuer names are displayed. The val 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="naccept-int">-naccept +int</dt>
<dd>

The server will exit after receiving the specified number of connections, default unlimited.

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

A file containing one or more blocks of PEM data. Each PEM block must encode a TLS ServerHello extension (2 bytes type, 2 bytes length, followed by &quot;length&quot; bytes of extension data). If the client sends an empty TLS ClientHello extension matching the type, the corresponding ServerHello extension will be returned.

</dd>
<dt id="certform-PEM-DER">-certform PEM|DER</dt>
<dd>

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

</dd>
<dt id="key-infile">-key infile</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="pass-val">-pass val</dt>
<dd>

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

</dd>
<dt id="dcert-infile--dkey-infile">-dcert infile, -dkey infile</dt>
<dd>

Specify an additional certificate and private key, these behave in the same manner as the -cert and -key options except there is no default if they are not specified (no additional certificate and key is used). As noted above some cipher suites require a certificate containing a key of a certain type. Some cipher suites need a certificate carrying an RSA key and some a DSS (DSA) key. By using RSA and DSS certificates and keys a server can support clients which only support RSA or DSS cipher suites by using an appropriate certificate.

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

A file containing trusted certificates to use when attempting to build the server certificate chain when a certificate specified via the -dcert option is in use.

</dd>
<dt id="dcertform-PEM-DER--dkeyform-PEM-DER--dpass-val">-dcertform PEM|DER, -dkeyform PEM|DER, -dpass val</dt>
<dd>

Additional certificate and private key format and passphrase respectively.

</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 server.

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

Specify whether the application should build the certificate chain to be provided to the client 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="nbio_test">-nbio_test</dt>
<dd>

Tests non blocking I/O.

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

This option translated a line feed from the terminal into CR+LF.

</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="msgfile-outfile">-msgfile outfile</dt>
<dd>

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

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

Prints the SSL session states.

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

A file containing trusted certificates to use during client authentication and to use when attempting to build the server certificate chain. The list is also used in the list of acceptable client CAs passed to the client when a certificate is requested.

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

The directory to use for client 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 server certificate chain.

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

The directory to use for building the chain provided to the client. 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 server 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="nocert">-nocert</dt>
<dd>

If this option is set then no certificate is used. This restricts the cipher suites available to the anonymous ones (currently just anonymous DH).

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

Inhibit printing of session and certificate information.

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

Sends a status message back to the client when it connects. This includes information about the ciphers used and various session parameters. The output is in HTML format so this option will normally be used with a web browser. Cannot be used in conjunction with -early_data.

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

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

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

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

Emulates a simple web server. Pages will be resolved relative to the current directory, for example if the URL https://myhost/page.html is requested the file ./page.html will be loaded. The files loaded are assumed to contain a complete and correct HTTP response (lines that are part of the HTTP response line and headers must end with CRLF). Cannot be used in conjunction with -early_data.

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

Generate SSL/TLS session IDs prefixed by val. This is mostly useful for testing any SSL/TLS code (e.g. proxies) that wish to deal with multiple servers, when each of which might be generating a unique range of session IDs (e.g. with a certain prefix).

</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="verify_return_error">-verify_return_error</dt>
<dd>

Verification errors normally just print a message but allow the connection to continue, for debugging purposes. If this option is used, then verification errors close the connection.

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

Enables certificate status request support (aka OCSP stapling).

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

Enables certificate status request support (aka OCSP stapling) and gives a verbose printout of the OCSP response.

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

Sets the timeout for OCSP response to int seconds.

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

Sets a fallback responder URL to use if no responder URL is present in the server certificate. Without this option an error is returned if the server certificate does not contain a responder address.

</dd>
<dt id="status_file-infile">-status_file infile</dt>
<dd>

Overrides any OCSP responder URLs from the certificate and always provides the OCSP Response stored in the file. The file must be in DER format.

</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="brief">-brief</dt>
<dd>

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

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

Simple test server which just reverses the text received from the client and sends it back to the server. Also sets -brief. Cannot be used in conjunction with -early_data.

</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="ssl2--ssl3--tls1--tls1_1--tls1_2--tls1_3--no_ssl2--no_ssl3--no_tls1--no_tls1_1--no_tls1_2--no_tls1_3">-ssl2, -ssl3, -tls1, -tls1_1, -tls1_2, -tls1_3, -no_ssl2, -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_server will negotiate the highest mutually supported protocol version. When a specific TLS version is required, only that version will be accepted from the client. Note that not all protocols and flags may be available, depending on how OpenSSL was built.

</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="no_comp">-no_comp</dt>
<dd>

Disable negotiation of TLS compression. TLS compression is not recommended and is off by default as of OpenSSL 1.1.0.

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

Enable negotiation of 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_ticket">-no_ticket</dt>
<dd>

Disable RFC4507bis session ticket support. This option has no effect if TLSv1.3 is negotiated. See -num_tickets.

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

Control the number of tickets that will be sent to the client after a full handshake in TLSv1.3. The default number of tickets is 2. This option does not affect the number of tickets sent after a resumption handshake.

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

Use the server&#39;s cipher preferences, rather than the client&#39;s preferences.

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

Prioritize ChaCha ciphers when preferred by clients. Requires -serverpref.

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

Set the SSL_OP_NO_SESSION_RESUMPTION_ON_RENEGOTIATION option.

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

Signature algorithms to support for client certificate authentication (colon-separated list).

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

Specifies the elliptic curve to use. NOTE: this is single curve, not a list. For a list of all possible curves, use:

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

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

This allows the list of TLSv1.2 and below ciphersuites used by the server to be modified. This list is combined with any TLSv1.3 ciphersuites that have been configured. When the client sends a list of supported ciphers the first client cipher also included in the server list is used. Because the client specifies the preference order, the order of the server cipherlist is irrelevant. See the ciphers command for more information.

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

This allows the list of TLSv1.3 ciphersuites used by the server to be modified. This list is combined with any TLSv1.2 and below ciphersuites that have been configured. When the client sends a list of supported ciphers the first client cipher also included in the server list is used. Because the client specifies the preference order, the order of the server cipherlist is irrelevant. 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="dhparam-infile">-dhparam infile</dt>
<dd>

The DH parameter file to use. The ephemeral DH cipher suites generate keys using a set of DH parameters. If not specified then an attempt is made to load the parameters from the server certificate file. If this fails then a static set of parameters hard coded into the s_server program will be used.

</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 different peer certificate verification options. See the <a href="../man1/verify.html">verify(1)</a> manual page for details.

</dd>
<dt id="crl_check--crl_check_all">-crl_check, -crl_check_all</dt>
<dd>

Check the peer certificate has not been revoked by its CA. The CRL(s) are appended to the certificate file. With the -crl_check_all option all CRLs of all CAs in the chain are checked.

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

Turns on non blocking I/O.

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

Expect the client to send PSK identity val when using a PSK cipher suite, and warn if they do not. By default, the expected PSK identity is the string &quot;Client_identity&quot;.

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

Use the PSK identity hint val when using a PSK cipher suite.

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

Use the PSK key val 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="listen">-listen</dt>
<dd>

This option can only be used in conjunction with one of the DTLS options above. With this option s_server will listen on a UDP port for incoming connections. Any ClientHellos that arrive will be checked to see if they have a cookie in them or not. Any without a cookie will be responded to with a HelloVerifyRequest. If a ClientHello with a cookie is received then s_server will connect to that peer and complete the handshake.

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

These options make s_server use DTLS protocols instead of TLS. With -dtls, s_server will negotiate any supported DTLS protocol version, whilst -dtls1 and -dtls1_2 will only support DTLSv1.0 and DTLSv1.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="no_dhe">-no_dhe</dt>
<dd>

If this option is set then no DH parameters will be loaded effectively disabling the ephemeral DH cipher suites.

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

These flags enable the Application-Layer Protocol Negotiation or Next Protocol Negotiation (NPN) extension, respectively. ALPN is the IETF standard and replaces NPN. The val list is a comma-separated list of supported protocol names. 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;. The flag -nextprotoneg cannot be specified if -tls1_3 is used.

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

Specifying an engine (by its unique id string in val) will cause s_server 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="keylogfile-outfile">-keylogfile outfile</dt>
<dd>

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

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

Change the default maximum early data bytes that are specified for new sessions and any incoming early data (when used in conjunction with the -early_data flag). The default value is approximately 16k. The argument must be an integer greater than or equal to 0.

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

Accept early data where possible. Cannot be used in conjunction with -www, -WWW, -HTTP or -rev.

</dd>
<dt id="anti_replay--no_anti_replay">-anti_replay, -no_anti_replay</dt>
<dd>

Switches replay protection on or off, respectively. Replay protection is on by default unless overridden by a configuration file. When it is on, OpenSSL will automatically detect if a session ticket has been used more than once, TLSv1.3 has been negotiated, and early data is enabled on the server. A full handshake is forced if a session ticket is used a second or subsequent time. Any early data that was sent will be rejected.

</dd>
</dl>

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

If a connection request is established with an SSL client and neither the -www nor the -WWW option has been used then normally any data received from the client is displayed and any key presses will be sent to the client.

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 but still accept new connections.

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

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="R">R</dt>
<dd>

Renegotiate the SSL session and request a client certificate (TLSv1.2 and below only).

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

Send some plain text down the underlying TCP connection: this should cause the client to disconnect due to a protocol violation.

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

Print out some session cache status information.

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

Send a heartbeat message to the client (DTLS only)

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

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

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

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

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

Send a certificate request to the client (TLSv1.3 only)

</dd>
</dl>

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

s_server can be used to debug SSL clients. To accept connections from a web browser the command:

<pre><code> openssl s_server -accept 443 -www</code></pre>

can be used for example.

Although specifying an empty list of CAs when requesting a client certificate is strictly speaking a protocol violation, some SSL clients interpret this to mean any CA is acceptable. This is useful for debugging purposes.

The session parameters can printed out using the sess_id program.

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

The output of common ciphers is wrong: it just gives the list of ciphers that OpenSSL recognizes and the client supports.

There should be a way for the s_server program to print out details of any unknown cipher suites a client says it supports.

<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_client.html">s_client(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 -allow-no-dhe-kex and -prioritize_chacha options were 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