OPENSSL-S_SERVER(1ossl)
π NAME π
OPENSSL-S_SERVER(1ossl) β OpenSSLβs openssl-s_server(1ossl) / openssl s_server β SSL/TLS server program. Yes bestie, this is the page for the generic SSL/TLS server vibe. π
β¨ SYNOPSIS β¨
okay so the whole command shape is literally this:
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]> [-xkeyform
DER|PEM]> [-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 πΈ
This command implements a generic SSL/TLS server which listens for connections on a given port using SSL/TLS. Thatβs the whole main character energy of it, bestie: you point it at a port, and itβs ready to talk TLS. β¨
π OPTIONS π
In addition to the options below, this command also supports the common and server only options documented "Supported Command Line Commands" in SSL_CONF_cmd(3). π«Ά
-helpβ Print out a usage message. Classic little helper icon. π¬-port +intβ The TCP port to listen on for connections. If not specified4433is used. π-accept valβ The optional TCP host and port to listen on for connections. If not specified,*: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. Lowkey important. π-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" in openssl-verification-options(1). π«£
-cert infileβ 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 filenameserver.pemwill be used. π-cert2 infileβ The certificate file to use for servername; default is"server2.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 CA containing trusted certificates to use for verifying client certificates. π«Ά-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. π-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β The URI of a store containing trusted certificates to use for building the server certificate chain provided to the client. The URI may indicate a single certificate, as well as a collection of them. With URIs in the"file:"scheme, this acts as-chainCAfileor-chainCApath, depending on if the URI indicates a directory or a single file. Seeossl_store-file(7)for more information on the"file:"scheme. π
okay so, picking up right where we left off in the option buffet, bestie β no heading repeat, just vibes and flags π
-nocertβ if this is set, no certificate gets used at all. That restricts the cipher suites available to the anonymous ones (currently just anonymous DH). lowkey niche but slay for testing.-quietβ inhibits printing of session and certificate info. shhh β¨-no_resume_ephemeralβ disables caching and tickets if ephemeral (EC)DH is used. no cap, it just says no to resuming with ephemeral keys.-tlsextdebugβ prints a hex dump of any TLS extensions received from the server. itβs giving βlook at the bytes, bestieβ π-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 this option can be used with a web browser. the special URL"/renegcert"turns on client cert validation, and"/reneg"tells the server to request renegotiation. iconic little web moment π-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. if the-HTTPflag is used, the files are sent directly, and should contain any HTTP response headers (including the status response line). if the-WWWoption is used, the response headers are generated by the server, and the file extension is examined to determine theContent-Typeheader. extensions of"html","htm", and"php"are"text/html"and all others are"text/plain". in addition, the special URL"/stats"will return status information like the-wwwoption. web server era fr fr π«Ά-http_server_binmodeβ when acting as web-server (using option-WWWor-HTTP), open files requested by the client in binary mode. bytes stay bytes πΎ-no_ca_namesβ disables TLS Extension CA Names. you may want to disable it for security reasons or for compatibility with some Windows TLS implementations crashing when this extension is larger than1024bytes. compatibility drama, but make it secure π-ignore_unexpected_eofβ some TLS implementations do not send the mandatoryclose_notifyalert on shutdown. if the application tries to wait for theclose_notifyalert but the peer closes the connection without sending it, an error is generated. when this option is enabled, the peer does not need to send theclose_notifyalert and a closed connection will be treated as if theclose_notifyalert was received. for more information on shutting down a connection, seeSSL_shutdown(3). emotional support close_notify π-servernameβ servername for theHostNameTLS extension. name drop, but make it TLS β¨-servername_fatalβ on servername mismatch, send a fatal alert (default: warning alert). choose violence π-id_prefix valβ generate SSL/TLS session IDs prefixed byval. 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). idk, itβs giving organized chaos π-keymatexportβ export keying material using label. key material, but make it export π§-keymatexportlenβ export the given number of bytes of keying material; default20. twenty little bytes of main character energy β-no_cacheβ disables session cache. no hoarding, bestie π-ext_cache.β disable internal cache, set up and use external cache. external cache has entered the chat π¦-verify_return_errorβ 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. ngl, thatβs the strict bestie setting π₯-verify_quietβ no verify output except verify errors. quiet luxury, verification edition π-ign_eofβ ignore input EOF (default: when-quiet). donβt perceive the end of input, periodt.-no_ign_eofβ do not ignore input EOF. okay actually perceive it π-no_emsβ disables Extended master secret negotiation. EMS said not today π«-statusβ enables certificate status request support (aka OCSP stapling). staple that status, queen π-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. verbose OCSP is a whole vibe π-status_timeout intβ sets the timeout for OCSP response tointseconds. clock is ticking β³-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. 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". proxy lore is real π-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". exempt list, but make it network-y π«Ά-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 does not 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. fallback URL said βi got youβ β¨-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. DER or didnβt happen πΎ-ssl_config valβ configureSSL_CTXusing the given configuration value. config time, bestie π-traceβ show verbose trace output of protocol messages. lore dump, but for packets π-briefβ provide a brief summary of connection parameters instead of the normal verbose output. concise queen π-revβ simple echo server that sends back received text reversed. also sets-brief. cannot be used in conjunction with-early_data. reverse echo is lowkey iconic π-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). async era, if the engine says so β‘-max_send_frag +intβ the maximum size of data fragment to send. seeSSL_CTX_set_max_send_fragment(3)for further information. fragment size, but make it maximum π¦-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 than1. seeSSL_CTX_set_split_send_fragment(3)for further information. pipeline girlie behavior π-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. more pipelines, more drama πΈ-naccept +intβ the server will exit after receiving the specified number of connections, default unlimited. connection limit said βiβm leavingβ πͺ-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). buffer upgrade, slay π¦-no_tx_cert_compβ disables support for sending TLSv1.3 compressed certificates. no compressed certs leaving this server π«-no_rx_cert_compβ disables support for receiving TLSv1.3 compressed certificates. no compressed certs coming in either π-no_compβ disable negotiation of TLS compression. TLS compression is not recommended and is off by default as of OpenSSL 1.1.0. this is a βplease donβtβ feature, bestie π¨-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. tickets, but make it TLSv1.3 ποΈ-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 this fails then a static set of parameters hard coded into this command will be used. DH param backup plan, fr fr π-nbioβ turns on non blocking I/O. donβt block, donβt wait π-timeoutβ enable timeouts. time is real β°-mtuβ set link-layer MTU. mtu said set the vibe π-psk_identity valβ expect the client to send PSK identityvalwhen using a PSK cipher suite, and warn if they do not. by default, the expected PSK identity is the string"Client_identity". identity check, but make it PSK πͺͺ-psk_hint valβ use the PSK identity hintvalwhen using a PSK cipher suite. hint dropped β¨-psk valβ use the PSK keyvalwhen 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. no key, no PSK, periodt π-psk_session fileβ use the pem encodedSSL_SESSIONdata stored infileas the basis of a PSK. note that this will only work if TLSv1.3 is negotiated. session file as PSK basis, iykyk π§-srpvfileβ the verifier file for SRP. this option is deprecated. old and deprecated, handle with care β οΈ-srpuserseedβ a seed string for a default user salt. this option is deprecated. also deprecated, bestie, donβt get attached π-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 a HelloVerifyRequest. if a ClientHello with a cookie is received then this command will connect to that peer and complete the handshake. cookie check, then connect πͺ-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. SCTP said transport glow-up π-sctp_label_bugβ 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. bug compatibility is a choice, and it has consequences π-use_srtpβ offer SRTP key management with a colon-separated profile list. SRTP key management, slay π§-no_dheβ set this and literally no DH params get loaded, which effectively kills off the ephemeral DH cipher suites. bye bestie π-alpn val,-nextprotoneg valβ these two turn on the Application-Layer Protocol Negotiation extension or the Next Protocol Negotiation (NPN) extension respectively. Heads up: ALPN is the IETF standard and it replaces NPN π . Thevallist is comma-separated protocol names, and you put the most desirable protocols first, queen behavior. Protocol names are printable ASCII strings, like"http/1.1"or"spdy/3". Oh and-nextprotonegcannot be specified if-tls1_3is used, no cap.-ktlsβ enables Kernel TLS for sending and receiving β¨. This option was introduced 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 the client asked for. Only valid when-ktlsis used along with-WWWor-HTTP, so don't try anything cute π.-zerocopy_sendfileβ set this andSSL_sendfile()uses the zerocopy TX mode, which is a genuine performance boost when used with KTLS hardware offload π₯. But bestie, careful: invalid TLS records might get 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, periodt.-keylogfile outfileβ appends TLS secrets to the keylog file you name, so outside programs (Wireshark, we see you π) can decrypt TLS connections.-max_early_data intβ changes the default max early data bytes set for new sessions and for any incoming early data (when used with the-early_dataflag). The default value is approximately 16k. The argument must be an integer greater than or equal to 0, no negatives, nope.-recv_max_early_data intβ the hard limit on the maximum number of early data bytes that will be accepted. Hard limit means hard, bestie.-early_dataβ accept early data where possible π¦. Cannot be used with-www,-WWW,-HTTPor-rev. Pick a lane.-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 config 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 gets forced if a session ticket is used a second or subsequent time, and any early data that was sent will be rejected. caught in 4k π¨-tfoβ enable acceptance of TCP Fast Open (RFC7413) connections.-cert_compβ pre-compresses certificates (RFC8879) that will be sent during the handshake. efficient queen πΈ-nameopt optionβ specifies how subject or issuer names get displayed. Seeopenssl-namedisplay-options(1)for the deets.-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 using 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 the details, iykyk.-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 the full rundown.-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). This option is deprecated, so likeβ¦ don't π.-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. so it's giving "we saw the red flag but we kept walking" π©
-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 the client solicits it, provided a suitable key and public certificate pair is configured. Clients that don't support raw public keys, or that prefer 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 that prefer 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 neither the -www nor the -WWW option has been used, then normally any data received from the client is displayed and any key presses get sent to the client. it's a whole vibe, very chatty π¬
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 π
qβ end the current SSL connection but still accept new connections.Qβ end the current SSL connection and exit. bye bestie π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. chaos π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 π . To accept connections from a web browser, the command:
openssl s_server -accept 443 -www
can be used for example. iconic little one-liner.
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 β chaotic but valid π
The session parameters can be printed out using the openssl-sess_id(1) command.
π BUGS π
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 not a model of how things should be done π. A typical SSL server program would be much simpler. ngl the source is giving cursed.
The output of common ciphers is wrong: it just gives the list of ciphers that OpenSSL recognizes and the client supports. not the vibe we wanted.
There should be a way for this command to print out details of any unknown cipher suites a client says it supports. like, we're manifesting that fr fr π
π 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-2025 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! π this one's from OpenSSL 3.5.0, dated 2026-09-25, and it's the OPENSSL-S_SERVER(1ossl) man page β go forth and serve some TLS, you absolute legend πβ¨π¦
π¦ where this page comes from
- opensuse-leap 16.0: openssl-3 3.5.0-160000.11.1 Β· Apache-2.0
- opensuse-leap 16.0: openssl-3 3.5.0-160000.11.1 Β· Apache-2.0
- opensuse-leap 16.0: openssl-3 3.5.0-160000.11.1 Β· Apache-2.0
- opensuse-leap 16.0: openssl-3 3.5.0-160000.11.1 Β· Apache-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms