B<openssl> B<s_server>
[B<-accept port>]
+[B<-naccept count>]
[B<-context id>]
[B<-verify depth>]
[B<-Verify depth>]
[B<-no_tls1>]
[B<-no_dhe>]
[B<-bugs>]
+[B<-brief>]
[B<-hack>]
[B<-www>]
[B<-WWW>]
[B<-no_ticket>]
[B<-id_prefix arg>]
[B<-rand file(s)>]
+[B<-serverinfo file>]
=head1 DESCRIPTION
=head1 OPTIONS
+In addition to the options below the B<s_server> utility also supports the
+common and server only options documented in the
+L<SSL_CONF_cmd(3)|SSL_CONF_cmd(3)/SUPPORTED COMMAND LINE COMMANDS> manual
+page.
+
=over 4
=item B<-accept port>
the TCP port to listen on for connections. If not specified 4433 is used.
+=item B<-naccept count>
+
+The server will exit after receiving B<number> connections, default unlimited.
+
=item B<-context id>
sets the SSL context id. It can be given any string value. If this option
show all protocol messages with hex dump.
+=item B<-trace>
+
+show verbose trace output of protocol messages. OpenSSL needs to be compiled
+with B<enable-ssl-trace> for this option to work.
+
+=item B<-msgfile>
+
+file to send output of B<-msg> or B<-trace> to, default standard output.
+
=item B<-nbio_test>
tests non blocking I/O
there are several known bug in SSL and TLS implementations. Adding this
option enables various workarounds.
+=item B<-brief>
+
+only provide a brief summary of connection parameters instead of the
+normal verbose output.
+
=item B<-hack>
this option enables a further workaround for some some early Netscape
assumed to contain a complete and correct HTTP response (lines that
are part of the HTTP response line and headers must end with CRLF).
+=item B<-rev>
+
+simple test server which just reverses the text received from the client
+and sends it back to the server. Also sets B<-brief>.
+
=item B<-engine id>
specifying an engine (by its unique B<id> string) will cause B<s_server>
The separator is B<;> for MS-Windows, B<,> for OpenVMS, and B<:> for
all others.
+=item B<-serverinfo file>
+
+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.
+
=back
=head1 CONNECTED COMMANDS