SERVER(1) OpenSL SERVER(1)
NAME
sserver - SL/TLS server program
SYNOPSIS
openssl sserver [-accept port] [-context id] [-verify depth] [-Verify
depth] [-cert filename] [-key keyfile] [-dcert filename] [-dkey key-
file] [-dhparam filename] [-nbio] [-nbiotest] [-crlf] [-debug] [-msg]
[-state] [-CApath directory] [-CAfile filename] [-nocert] [-cipher
cipherlist] [-quiet] [-notmprsa] [-ssl2] [-ssl3] [-tls1] [-nossl2]
[-nossl3] [-notls1] [-nodhe] [-bugs] [-hack] [-www] [-W] [-HTP]
[-engine id] [-idprefix arg] [-rand file(s)]
DESCRIPTION
The sserver command implements a generic SL/TLS server which listens
for connections on a given port using SL/TLS.
OPTIONS
-accept port
the TCP port to listen on for connections. If not specified 4433 is
used.
-context id
sets the SL context id. It can be given any string value. If this
option is not present a default value will be used.
-cert certname
The certificate to use, most servers cipher suites require the use
of a certificate and some require a certificate with a certain pub-
lic key type: for example the DS cipher suites require a certifi-
cate containing a DS (DSA) key. If not specified then the filename
"server.pem" will be used.
-key keyfile
The private key to use. If not specified then the certificate file
will be used.
-dcert filename, -dkey keyname
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 certifi-
cate containing a key of a certain type. Some cipher suites need a
certificate carrying an RSA key and some a DS (DSA) key. By using
RSA and DS certificates and keys a server can support clients
which only support RSA or DS cipher suites by using an appropriate
certificate.
-nocert
if this option is set then no certificate is used. This restricts
the cipher suites available to the anonymous ones (currently just
anonymous DH).
-dhparam filename
the DH parameter file to use. The ephemeral DH cipher suites gener-
ate 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 sserver program will be used.
-nodhe
if this option is set then no DH parameters will be loaded effec-
tively disabling the ephemeral DH cipher suites.
-notmprsa
certain export cipher suites sometimes use a temporary RSA key,
this option disables temporary RSA key generation.
-verify depth, -Verify depth
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.
-CApath directory
The directory to use for client certificate verification. This
directory must be in "hash format", see verify for more informa-
tion. These are also used when building the server certificate
chain.
-CAfile file
A file containing trusted certificates to use during client authen-
tication 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.
-state
prints out the SL session states.
-debug
print extensive debugging information including a hex dump of all
traffic.
-msg
show all protocol messages with hex dump.
-nbiotest
tests non blocking I/O
-nbio
turns on non blocking I/O
-crlf
this option translated a line feed from the terminal into CR]LF.
-quiet
inhibit printing of session and certificate information.
-ssl2, -ssl3, -tls1, -nossl2, -nossl3, -notls1
these options disable the use of certain SL or TLS protocols. By
default the initial handshake uses a method which should be compat-
ible with all servers and permit them to use SL v3, SL v2 or TLS
as appropriate.
-bugs
there are several known bug in SL and TLS implementations. Adding
this option enables various workarounds.
-hack
this option enables a further workaround for some some early
Netscape SL code (?).
-cipher cipherlist
this allows the cipher list used by the server to be modified.
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
irrelevant. See the ciphers command for more information.
-www
sends a status message back to the client when it connects. This
includes lots of 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.
-W
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.
-HTP
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 cor-
rect HTP response (lines that are part of the HTP response line
and headers must end with CRLF).
-engine id
specifying an engine (by it's unique id string) will cause sserver
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.
-idprefix arg
generate SL/TLS session IDs prefixed by arg. This is mostly useful
for testing any SL/TLS code (eg. proxies) that wish to deal with
multiple servers, when each of which might be generating a unique
range of session IDs (eg. with a certain prefix).
-rand file(s)
a file or files containing random data used to seed the random num-
ber generator, or an EGD socket (see RANDegd(3)). Multiple files
can be specified separated by a OS-dependent character. The sepa-
rator is ;; for MS-Windows, ,, for OpenVMS, and :: for all others.
CONECTED COMANDS
If a connection request is established with an SL client and neither
the -www nor the -W 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 single letter commands are also recognized which perform spe-
cial operations: these are listed below.
q end the current SL connection but still accept new connections.
Q end the current SL connection and exit.
r renegotiate the SL session.
R renegotiate the SL session and request a client certificate.
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.
NOTES
sserver can be used to debug SL clients. To accept connections from a
web browser the command:
openssl sserver -accept 443 -www
can be used for example.
Most web browsers (in particular Netscape and MSIE) only support RSA
cipher suites, so they cannot connect to servers which don't use a cer-
tificate carrying an RSA key or a version of OpenSL with RSA disabled.
Although specifying an empty list of CAs when requesting a client cer-
tificate is strictly speaking a protocol violation, some SL clients
interpret this to mean any CA is acceptable. This is useful for debug-
ging purposes.
The session parameters can printed out using the sessid program.
BUGS
Because this program has a lot of options and also because some of the
techniques used are rather old, the C source of sserver is rather hard
to read and not a model of how things should be done. A typical SL
server program would be much simpler.
The output of common ciphers is wrong: it just gives the list of
ciphers that OpenSL recognizes and the client supports.
There should be a way for the sserver program to print out details of
any unknown cipher suites a client says it supports.
SEE ALSO
sessid(1), sclient(1), ciphers(1)
0.9.7l 2003-03-20 SERVER(1)
|
