OPENSSL-S_SERVER(1ossl)
๐ NAME ๐
openssl-s_server โ SSL/TLS server program. Yup, that's the whole NAME vibe, and this page is OPENSSL-S_SERVER(1ossl), so you're literally in the right group chat. ๐
โจ SYNOPSIS โจ
openssl s_server [-help] [-port +int] [-accept val] [-unix val] [-4]
[-6] [-unlink] [-context val] [-verify int] [-Verify int] [-cert infile]
[-cert2 infile] [-certform DER|PEM|P12] [-cert_chain infile]
[-build_chain] [-serverinfo val] [-key filename|uri] [-key2
filename|uri] [-keyform DER|PEM|P12|ENGINE] [-pass val] [-dcert infile]
[-dcertform DER|PEM|P12] [-dcert_chain infile] [-dkey filename|uri]
[-dkeyform DER|PEM|P12|ENGINE] [-dpass val] [-nbio_test] [-crlf]
[-debug] [-msg] [-msgfile outfile] [-state] [-nocert] [-quiet]
[-no_resume_ephemeral] [-www] [-WWW] [-http_server_binmode]
[-no_ca_names] [-ignore_unexpected_eof] [-servername]
[-servername_fatal] [-tlsextdebug] [-HTTP] [-id_prefix val]
[-keymatexport val] [-keymatexportlen +int] [-CRL infile] [-CRLform
DER|PEM] [-crl_download] [-chainCAfile infile] [-chainCApath dir]
[-chainCAstore uri] [-verifyCAfile infile] [-verifyCApath dir]
[-verifyCAstore uri] [-no_cache] [-ext_cache] [-verify_return_error]
[-verify_quiet] [-ign_eof] [-no_ign_eof] [-no_ems] [-status]
[-status_verbose] [-status_timeout int] [-proxy
[http[s]://][userinfo@]host[:port][/path][?query][#fragment]] [-no_proxy
addresses] [-status_url val] [-status_file infile] [-ssl_config val]
[-trace] [-security_debug] [-security_debug_verbose] [-brief] [-rev]
[-async] [-max_send_frag +int] [-split_send_frag +int] [-max_pipelines
+int] [-naccept +int] [-read_buf +int] [-no_tx_cert_comp]
[-no_rx_cert_comp] [-dhparam infile] [-nbio] [-psk_identity val]
[-psk_hint val] [-psk val] [-psk_session file] [-srpvfile infile]
[-srpuserseed val] [-timeout] [-mtu +int] [-listen] [-sctp]
[-sctp_label_bug] [-use_srtp val] [-no_dhe] [-nextprotoneg val] [-alpn
val] [-ktls] [-sendfile] [-zerocopy_sendfile] [-keylogfile outfile]
[-recv_max_early_data int] [-max_early_data int] [-early_data]
[-stateless] [-anti_replay] [-no_anti_replay] [-num_tickets] [-tfo]
[-cert_comp] [-nameopt option] [-no_ssl3] [-no_tls1] [-no_tls1_1]
[-no_tls1_2] [-no_tls1_3] [-ssl3] [-tls1] [-tls1_1] [-tls1_2] [-tls1_3]
[-dtls] [-dtls1] [-dtls1_2] [-allow_proxy_certs] [-attime timestamp]
[-no_check_time] [-check_ss_sig] [-crl_check] [-crl_check_all]
[-explicit_policy] [-extended_crl] [-ignore_critical] [-inhibit_any]
[-inhibit_map] [-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] [-verify_depth num] [-verify_email email]
[-verify_hostname hostname] [-verify_ip ip] [-verify_name name]
[-x509_strict] [-issuer_checks] [-bugs] [-no_comp] [-comp] [-no_ticket]
[-serverpref] [-client_renegotiation] [-legacy_renegotiation]
[-no_renegotiation] [-no_resumption_on_reneg] [-legacy_server_connect]
[-no_legacy_server_connect] [-no_etm] [-allow_no_dhe_kex]
[-prefer_no_dhe_kex] [-prioritize_chacha] [-strict] [-sigalgs algs]
[-client_sigalgs algs] [-groups groups] [-curves curves] [-named_curve
curve] [-cipher ciphers] [-ciphersuites 1.3ciphers] [-min_protocol
minprot] [-max_protocol maxprot] [-record_padding padding]
[-debug_broken_protocol] [-no_middlebox] [-xkey infile] [-xcert file]
[-xchain file] [-xchain_build file] [-xcertform DER|PEM|P12]> [-xkeyform
DER|PEM|P12]> [-CAfile file] [-no-CAfile] [-CApath dir] [-no-CApath]
[-CAstore uri] [-no-CAstore] [-rand files] [-writerand file] [-engine
id] [-provider name] [-provider-path path] [-provparam [name:]key=value]
[-propquery propq] [-enable_server_rpk] [-enable_client_rpk]
๐ธ DESCRIPTION ๐ธ
Okay so this command is literally a generic SSL/TLS server. It listens for connections on a given port using SSL/TLS. Main character energy for your terminal, no cap. ๐ซถ
๐ OPTIONS ๐
Heads up bestie: besides the options down below, this command also supports the common options and the server-only options documented under "Supported Command Line Commands" in SSL_CONF_cmd(3). โจ
-helpโ Prints out a usage message. Your little SOS button, basically. ๐-port +intโ The TCP port to listen on for connections. If you don't specify it,4433is used. Default queen behavior. ๐-accept valโ The optional TCP host and port to listen on for connections. If you don't specify it,*:4433is used.-unix valโ Unix domain socket to accept on.-4โ Use IPv4 only.-6โ Use IPv6 only.-unlinkโ For-unix, unlink any existing socket first.-context valโ Sets the SSL context id. It can be given any string value. If this option is not present a default value will be used.-verify int,-Verify intโ 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-verifyoption a certificate is requested but the client does not have to send one; with the-Verifyoption 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. By default, validation of any supplied client certificate and its chain is done w.r.t. the (D)TLS Client ("sslclient") purpose. For details see "Certificate Extensions" inopenssl-verification-options(1).-cert infileโ The certificate to use. Most server 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 filenameserver.pemwill be used.-cert2 infileโ The certificate file to use for servername; default isserver2.pem.-certform DER|PEM|P12โ The server certificate file format; unspecified by default. Seeopenssl-format-options(1)for details.-cert_chainโ A file or URI of untrusted certificates to use when attempting to build the certificate chain related to the certificate specified via the-certoption. These untrusted certificates are sent to clients and used for generating certificate status (aka OCSP stapling) requests. The input can be in PEM, DER, or PKCS#12 format.-build_chainโ Specify whether the application should build the server certificate chain to be provided to the client.-serverinfo valโ 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"length"bytes of extension data). If the client sends an empty TLS ClientHello extension matching the type, the corresponding ServerHello extension will be returned.-key filename|uriโ The private key to use. If not specified then the certificate file will be used.-key2 filename|uriโ The private Key file to use for servername if not given via-cert2.-keyform DER|PEM|P12|ENGINEโ The key format; unspecified by default. Seeopenssl-format-options(1)for details.-pass valโ The private key and certificate file password source. For more information about the format of val, seeopenssl-passphrase-options(1).-dcert infile,-dkey filename|uriโ Specify an additional certificate and private key. These behave in the same manner as the-certand-keyoptions 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.-dcert_chainโ A file or URI of untrusted certificates to use when attempting to build the server certificate chain when a certificate specified via the-dcertoption is in use. The input can be in PEM, DER, or PKCS#12 format.-dcertform DER|PEM|P12โ The format of the additional certificate file; unspecified by default. Seeopenssl-format-options(1)for details.-dkeyform DER|PEM|P12|ENGINEโ The format of the additional private key; unspecified by default. Seeopenssl-format-options(1)for details.-dpass valโ The passphrase for the additional private key and certificate. For more information about the format of val, seeopenssl-passphrase-options(1).-nbio_testโ Tests non blocking I/O.-crlfโ This option translated a line feed from the terminal into CR+LF.-debugโ Print extensive debugging information including a hex dump of all traffic.-security_debugโ Print output from SSL/TLS security framework.-security_debug_verboseโ Print more output from SSL/TLS security framework.-msgโ Show all protocol messages with hex dump.-msgfile outfileโ File to send output of-msgor-traceto, default standard output.-stateโ Prints the SSL session states.-CRL infileโ The CRL file to use.-CRLform DER|PEMโ The CRL file format; unspecified by default. Seeopenssl-format-options(1)for details.-crl_downloadโ Download CRLs from distribution points given in CDP extensions of certificates.-verifyCAfile filenameโ A file in PEM format containing trusted CA certificates (root and/or intermediate) used to verify the client certificate chain.-verifyCApath dirโ A directory containing trusted certificates to use for verifying client certificates. This directory must be in "hash format", seeopenssl-verify(1)for more information.-verifyCAstore uriโ The URI of a store containing trusted certificates to use for verifying client certificates.
When any of -verifyCAfile, -verifyCApath, or -verifyCAstore is specified, they are loaded into a separate verification store (via SSL_CTX_set1_verify_cert_store(3)) and used for client certificate verification instead of the store built from -CAfile, -CApath, and -CAstore. Note that -CAfile is the sole source of acceptable issuing CA names sent to the client in the Certificate Request message during the handshake; -CApath, -CAstore, and the -verifyCA* options do not contribute to this list.
-chainCAfile fileโ A file in PEM format containing trusted certificates to use when attempting to build the server certificate chain.-chainCApath dirโ A directory containing trusted certificates to use for building the server certificate chain provided to the client. This directory must be in "hash format", seeopenssl-verify(1)for more information.-chainCAstore uriโ bestie, this is where you point at a store of trusted certs used to build the server certificate chain that gets handed to the client ๐. The URI can point at one single certificate or a whole collection of them. If it's a"file:"scheme URI, it acts like-chainCAfileor-chainCApathdepending on whether the URI points at a directory or a single file. Wanna know more about the"file:"scheme? Run, don't walk, toossl_store-file(7)๐ .-nocertโ set this and literally no certificate gets used โจ. Which means your cipher suites get restricted to the anonymous ones (currently just anonymous DH). That's the whole vibe, no cap.-quietโ inhibits printing of session and certificate info ๐คซ. Silence is golden, periodt.-no_resume_ephemeralโ disables caching and tickets whenever ephemeral (EC)DH is in play ๐ฆ.-tlsextdebugโ prints a hex dump of any TLS extensions received from the server ๐. Very "let me see the receipts" of you.-wwwโ sends a status message back to the client when it connects ๐. This includes info about the ciphers used and various session parameters. Output is in HTML format, so yes, you can absolutely point a web browser at it ๐. Bonus: the special URL"/renegcert"turns on client cert validation, and"/reneg"tells the server to request renegotiation. Iconic.-WWW,-HTTPโ emulates a simple web server ๐. Pages get resolved relative to the current directory โ so if the URL"https://myhost/page.html"is requested, the file./page.htmlwill be sent. With the-HTTPflag the files are sent directly and should contain any HTTP response headers (including the status response line). With the-WWWoption, the response headers are generated by the server, and the file extension gets examined to determine theContent-Typeheader. Extensions of"html","htm", and"php"are"text/html"and all others are"text/plain"๐. Also, the special URL"/stats"returns status information just like the-wwwoption. Slay.-http_server_binmodeโ when you're acting as a web server (using option-WWWor-HTTP), this opens the files the client requested in binary mode ๐ซถ.-no_ca_namesโ disables the TLS Extension CA Names โจ. You might wanna disable it for security reasons, or for compatibility with some Windows TLS implementations that literally crash when this extension is larger than 1024 bytes ๐ญ. Not the crash, bestie.-ignore_unexpected_eofโ okay so some TLS implementations don't send the mandatoryclose_notifyalert on shutdown ๐. If the application tries to wait for theclose_notifyalert but the peer just closes the connection without sending it, an error gets generated. Enable this option and the peer no longer needs to send theclose_notifyalert โ a closed connection gets treated as if theclose_notifyalert was received ๐. For more on shutting down a connection, seeSSL_shutdown(3).-servernameโ servername for the HostName TLS extension ๐ธ.-servername_fatalโ on servername mismatch, send a fatal alert (default: warning alert) โ ๏ธ. Choose your drama level wisely.-id_prefix valโ generates SSL/TLS session IDs prefixed by val ๐ . Mostly useful for testing any SSL/TLS code (e.g. proxies) that wishes to deal with multiple servers, when each of which might be generating a unique range of session IDs (e.g. with a certain prefix). iykyk.-keymatexportโ export keying material using label ๐ฅ.-keymatexportlenโ export the given number of bytes of keying material; default 20 โจ.-no_cacheโ disable session cache ๐ซ.-ext_cache.โ disable internal cache, set up and use external cache ๐ฆ. (Yes, that trailing dot is in the original โ we keep it exactly, no editing the source, bestie.)-verify_return_errorโ verification errors normally just print a message but allow the connection to continue, for debugging purposes ๐. Use this option and verification errors close the connection ๐. No more "it's fine, keep going".-verify_quietโ no verify output except verify errors ๐คซ.-ign_eofโ ignore input EOF (default: when-quiet) ๐.-no_ign_eofโ do not ignore input EOF ๐ซ.-no_emsโ disable Extended master secret negotiation ๐.-statusโ enables certificate status request support (aka OCSP stapling) ๐.-status_verboseโ enables certificate status request support (aka OCSP stapling) and gives a verbose printout of the OCSP response ๐. Use the-cert_chainoption to specify the certificate of the server's certificate signer that is required for certificate status requests.-status_timeout intโ sets the timeout for OCSP response to int seconds โฑ๏ธ.-proxy [http[s]://][userinfo@]host[:port][/path][?query][#fragment]โ the HTTP(S) proxy server to use for reaching the OCSP server unless-no_proxyapplies (see below, bestie) ๐. If the host string is an IPv6 address, it must be enclosed in"["and"]". The proxy port defaults to80or443if the scheme is"https"; apart from that, the optional"http://"or"https://"prefix is ignored, as well as any userinfo, path, query, and fragment components. Defaults to the environment variable"http_proxy"if set, else"HTTP_PROXY"in case no TLS is used, otherwise"https_proxy"if set, else"HTTPS_PROXY".-no_proxy addressesโ list of IP addresses and/or DNS names of servers not to use an HTTP(S) proxy for, separated by commas and/or whitespace (where in the latter case the whole argument must be enclosed in"...") ๐ . Default is from the environment variable"no_proxy"if set, else"NO_PROXY".-status_url valโ 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 doesn't contain a responder address. The optional userinfo and fragment URL components are ignored. Any given query component is handled as part of the path component.-status_file infileโ 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. No exceptions.-ssl_config valโ configureSSL_CTXusing the given configuration value โจ.-traceโ show verbose trace output of protocol messages ๐.-briefโ provide a brief summary of connection parameters instead of the normal verbose output ๐คซ.-revโ a simple echo server that sends back received text reversed ๐. Also sets-brief. Cannot be used in conjunction with-early_dataโ ๏ธ. Pick a lane, bestie.-asyncโ 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-engineoption. For test purposes the dummy async engine (dasync) can be used (if available). Test girl summer.-max_send_frag +intโ the maximum size of data fragment to send ๐ฆ. SeeSSL_CTX_set_max_send_fragment(3)for further information.-split_send_frag +intโ 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 bymax_pipelines. This only has an effect if a suitable cipher suite has been negotiated, an engine that supports pipelining has been loaded, andmax_pipelinesis greater than 1. SeeSSL_CTX_set_split_send_fragment(3)for further information.-max_pipelines +intโ 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. thedasyncengine) and a suitable cipher suite has been negotiated. The default value is1. SeeSSL_CTX_set_max_pipelines(3)for further information.-naccept +intโ the server will exit after receiving the specified number of connections, default unlimited ๐ช. Set your limit, diva.-read_buf +intโ 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 (seeSSL_CTX_set_default_read_buffer_len(3)for further information).-no_tx_cert_compโ disables support for sending TLSv1.3 compressed certificates ๐ซ.-no_rx_cert_compโ disables support for receiving TLSv1.3 compressed certificates ๐ซ.-no_compโ disable negotiation of TLS compression ๐ซ. TLS compression is not recommended and is off by default as of OpenSSL 1.1.0. So likeโฆ leave it alone, fr fr.-num_ticketsโ control the number of tickets that will be sent to the client after a full handshake in TLSv1.3 ๐๏ธ. The default number of tickets is2. This option does not affect the number of tickets sent after a resumption handshake.-dhparam infileโ 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 that fails then a static set of parameters hard coded into this command will be used. Hardcoded fallback, we love a backup plan ๐ .-nbioโ turns on non blocking I/O โก.-timeoutโ enable timeouts โฑ๏ธ.-mtuโ set link-layer MTU ๐.-psk_identity valโ expect the client to send PSK identity val when using a PSK cipher suite, and warn if they don't ๐ซถ. By default, the expected PSK identity is the string"Client_identity".-psk_hint valโ use the PSK identity hint val when using a PSK cipher suite โจ.-psk valโ use the PSK key val when using a PSK cipher suite ๐. The key is given as a hexadecimal number without leading0x, for example-psk 1a2b3c4d. This option must be provided in order to use a PSK cipher โ non-negotiable, bestie.-psk_session fileโ use the pem encodedSSL_SESSIONdata stored in file as the basis of a PSK ๐ธ. Note that this will only work if TLSv1.3 is negotiated.-srpvfileโ the verifier file for SRP โ ๏ธ. This option is deprecated. (RIP, we hardly knew ye.)-srpuserseedโ a seed string for a default user salt โ ๏ธ. This option is deprecated too. Same energy.-listenโ this option can only be used in conjunction with one of the DTLS options above ๐ง. With this option, this command 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 aHelloVerifyRequest. If a ClientHello with a cookie is received then this command will connect to that peer and complete the handshake. Cookies = the vibe check, apparently ๐ช.-sctpโ use SCTP for the transport protocol instead of UDP in DTLS ๐ฆ. Must be used in conjunction with-dtls,-dtls1or-dtls1_2. This option is only available where OpenSSL has support for SCTP enabled. Check your build first, bestie.-sctp_label_bugโ okay so this one makes you use the wrong behaviour that older OpenSSL builds have when they compute endpoint-pair shared secrets for DTLS/SCTP ๐ซ it lets you talk to those old broken implementations, but it also means you break interop with the correct ones. Gotta be used together with-sctp. And heads up: this option only exists where OpenSSL was built with SCTP support enabled.-use_srtpโ offer SRTP key management, with a colon-separated profile list.-no_dheโ set this and literally no DH parameters get loaded, which effectively disables the ephemeral DH cipher suites ๐-alpn val,-nextprotoneg valโ these flags turn on the Application-Layer Protocol Negotiation extension or the Next Protocol Negotiation (NPN) extension, respectively โจ ALPN is the IETF standard and it replaces NPN. Thevallist is a comma-separated list of supported protocol names, and you want the most desirable protocols first. Protocol names are printable ASCII strings, like"http/1.1"or"spdy/3". Ngl,-nextprotonegcannot be specified if-tls1_3is used.-ktlsโ enable Kernel TLS for sending and receiving ๐ฅ this option showed up in OpenSSL 3.2.0, and Kernel TLS is off by default as of OpenSSL 3.2.0.-sendfileโ if this is set and KTLS is enabled,SSL_sendfile()gets used instead ofBIO_write()to send the HTTP response a client asked for. Only valid when-ktlsis specified along with-WWWor-HTTP.-zerocopy_sendfileโ set this andSSL_sendfile()uses the zerocopy TX mode, which gives a performance boost when used with KTLS hardware offload โก but bestie, note that invalid TLS records might be transmitted if the file is changed while it's being sent ๐ญ this option depends on-sendfile; when used alone,-sendfileis implied and a warning is shown. Also note that KTLS sendfile on FreeBSD always runs in the zerocopy mode.-keylogfile outfileโ appends TLS secrets to the keylog file you name, so external programs (like Wireshark) can decrypt TLS connections ๐ต๏ธโโ๏ธ-max_early_data intโ changes the default max early data bytes specified for new sessions and any incoming early data (when used with the-early_dataflag). Default is approximately 16k. The argument must be an integer greater than or equal to 0.-recv_max_early_data intโ specifies the hard limit on the maximum number of early data bytes that will be accepted.-early_dataโ accept early data where possible. Cannot be used in conjunction with-www,-WWW,-HTTPor-rev.-statelessโ require TLSv1.3 cookies ๐ช-anti_replay,-no_anti_replayโ switches replay protection on or off, respectively. Replay protection is on by default unless overridden by a configuration file. When it's on, OpenSSL automatically detects 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, and any early data that was sent will be rejected.
Note that the server manages an internal cache of session tickets. If a client closes the connection without sending the close_notify alert, the corresponding session ticket is removed and a full handshake is forced.
-tfoโ enable acceptance of TCP Fast Open (RFC7413) connections ๐-cert_compโ pre-compresses certificates (RFC8879) that will be sent during the handshake.-nameopt optionโ specifies how the subject or issuer names are displayed. Seeopenssl-namedisplay-options(1)for details.-no_ssl3,-no_tls1,-no_tls1_1,-no_tls1_2,-no_tls1_3,-ssl3,-tls1,-tls1_1,-tls1_2,-tls1_3โ see "TLS Version Options" inopenssl(1).-dtls,-dtls1,-dtls1_2โ these specify the use of DTLS instead of TLS. See "TLS Version Options" inopenssl(1).-bugs,-comp,-no_comp,-no_ticket,-serverpref,-client_renegotiation,-legacy_renegotiation,-no_renegotiation,-no_resumption_on_reneg,-legacy_server_connect,-no_legacy_server_connect,-no_etm,-allow_no_dhe_kex,-prefer_no_dhe_kex,-prioritize_chacha,-strict,-sigalgs algs,-client_sigalgs algs,-groups groups,-curves curves,-named_curve curve,-cipher ciphers,-ciphersuites 1.3ciphers,-min_protocol minprot,-max_protocol maxprot,-record_padding padding,-debug_broken_protocol,-no_middleboxโ see "SUPPORTED COMMAND LINE COMMANDS" inSSL_CONF_cmd(3)for details.-xkey infile,-xcert file,-xchain file,-xchain_build file,-xcertform DER|PEM,-xkeyform DER|PEMโ set extended certificate verification options. See "Extended Verification Options" inopenssl-verification-options(1)for details.-CAfile file,-no-CAfile,-CApath dir,-no-CApath,-CAstore uri,-no-CAstoreโ see "Trusted Certificate Options" inopenssl-verification-options(1)for details.-rand files,-writerand fileโ see "Random State Options" inopenssl(1)for details.-engine idโ see "Engine Options" inopenssl(1). Heads up: this option is deprecated ๐-provider name,-provider-path path,-provparam [name:]key=value,-propquery propqโ see "Provider Options" inopenssl(1),provider(7), andproperty(7).-allow_proxy_certs,-attime,-no_check_time,-check_ss_sig,-crl_check,-crl_check_all,-explicit_policy,-extended_crl,-ignore_critical,-inhibit_any,-inhibit_map,-no_alt_chains,-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,-issuer_checksโ set various options of certificate chain verification. See "Verification Options" inopenssl-verification-options(1)for details.
If the server requests a client certificate, then verification errors are displayed, for debugging, but the command will proceed unless the -verify_return_error option is used.
-enable_server_rpkโ enable support for sending raw public keys (RFC7250) to the client. A raw public key will be sent by the server, if solicited by the client, provided a suitable key and public certificate pair is configured. Clients that don't support raw public keys or prefer to use X.509 certificates can still elect to receive X.509 certificates as usual.
Raw public keys are extracted from the configured certificate/private key.
-enable_client_rpkโ enable support for receiving raw public keys (RFC7250) from the client. Use of X.509 certificates by the client becomes optional, and clients that support raw public keys may elect to use them. Clients that don't support raw public keys or prefer to use X.509 certificates can still elect to send X.509 certificates as usual.
Raw public keys are extracted from the configured certificate/private key.
๐ฎ CONNECTED COMMANDS ๐ฎ
Okay so if a connection request gets established with an SSL client and you didn't use -www or -WWW, then normally any data received from the client gets displayed, and any key presses get sent to the client ๐
But certain commands are also recognized, and they do special operations โจ These commands are a single letter that must appear at the start of a line. Here they are:
qโ end the current SSL connection but still accept new connections.Qโ end the current SSL connection and exit.rโ renegotiate the SSL session (TLSv1.2 and below only).Rโ renegotiate the SSL session and request a client certificate (TLSv1.2 and below only).Pโ send some plain text down the underlying TCP connection: this should cause the client to disconnect due to a protocol violation ๐Sโ print out some session cache status information.kโ send a key update message to the client (TLSv1.3 only).Kโ send a key update message to the client and request one back (TLSv1.3 only).cโ send a certificate request to the client (TLSv1.3 only).
๐ NOTES ๐
This command can be used to debug SSL clients, fr. To accept connections from a web browser, the command:
openssl s_server -accept 443 -www
can be used for example ๐ซถ
And okay, technically specifying an empty list of CAs when requesting a client certificate is strictly speaking a protocol violation โ but some SSL clients interpret this to mean any CA is acceptable, which is genuinely useful for debugging purposes.
Also, the session parameters can be printed out using the openssl-sess_id(1) command โญ
๐ BUGS ๐
Real talk: because this program has a lot of options and also because some of the techniques used are rather old, the C source for this command is rather hard to read and honestly not a model of how things should be done ๐ญ a typical SSL server program would be much simpler.
Also, the output of common ciphers is wrong: it just gives the list of ciphers that OpenSSL recognizes and the client supports. That's it. That's the whole list.
And there should be a way for this command to print out details of any unknown cipher suites a client says it supports โ but there isn't ๐
๐ SEE ALSO ๐
openssl(1), openssl-sess_id(1), openssl-s_client(1), openssl-ciphers(1), SSL_CONF_cmd(3), SSL_CTX_set_max_send_fragment(3), SSL_CTX_set_split_send_fragment(3), SSL_CTX_set_max_pipelines(3), ossl_store-file(7)
๐ธ HISTORY ๐ธ
- The
-no_alt_chainsoption was added in OpenSSL 1.1.0. - The
-allow-no-dhe-kexand-prioritize_chachaoptions were added in OpenSSL 1.1.1. - The
-srpvfile,-srpuserseed, and-engineoption were deprecated in OpenSSL 3.0. - The
-enable_client_rpk,-enable_server_rpk,-no_rx_cert_comp,-no_tx_cert_comp, and-tfooptions were added in OpenSSL 3.2.
ยฉ๏ธ COPYRIGHT ยฉ๏ธ
Copyright 2000-2026 The OpenSSL Project Authors. All Rights Reserved.
Licensed under the Apache License 2.0 (the "License"). 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 <https://www.openssl.org/source/license.html>.
And that's the whole page bestie, you ATE that reading challenge ๐ this was OpenSSL 3.5.9, dated 2026-09-29, for OPENSSL-S_SERVER(1ossl) โ go forth and serve some TLS ๐โจ๐
๐ฆ where this page comes from
- alpine 3.23: openssl-doc 3.5.9-r0 ยท Apache-2.0
- alpine 3.24: openssl-doc 3.5.9-r0 ยท Apache-2.0
- ๐ girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms