s_client.pod 8.0 KB
Newer Older
1 2 3 4 5 6 7 8 9 10

=pod

=head1 NAME

s_client - SSL/TLS client program

=head1 SYNOPSIS

B<openssl> B<s_client>
L
Lutz Jänicke 已提交
11
[B<-connect host:port>]
R
Typo  
Richard Levitte 已提交
12
[B<-verify depth>]
13
[B<-cert filename>]
D
PR: 910  
Dr. Stephen Henson 已提交
14
[B<-certform DER|PEM>]
15
[B<-key filename>]
D
PR: 910  
Dr. Stephen Henson 已提交
16 17
[B<-keyform DER|PEM>]
[B<-pass arg>]
18 19 20 21 22 23
[B<-CApath directory>]
[B<-CAfile filename>]
[B<-reconnect>]
[B<-pause>]
[B<-showcerts>]
[B<-debug>]
B
Bodo Möller 已提交
24
[B<-msg>]
25 26 27 28
[B<-nbio_test>]
[B<-state>]
[B<-nbio>]
[B<-crlf>]
29
[B<-ign_eof>]
30 31 32 33 34 35 36 37 38
[B<-quiet>]
[B<-ssl2>]
[B<-ssl3>]
[B<-tls1>]
[B<-no_ssl2>]
[B<-no_ssl3>]
[B<-no_tls1>]
[B<-bugs>]
[B<-cipher cipherlist>]
39
[B<-starttls protocol>]
40
[B<-engine id>]
41
[B<-rand file(s)>]
42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62

=head1 DESCRIPTION

The B<s_client> command implements a generic SSL/TLS client which connects
to a remote host using SSL/TLS. It is a I<very> useful diagnostic tool for
SSL servers.

=head1 OPTIONS

=over 4

=item B<-connect host:port>

This specifies the host and optional port to connect to. If not specified
then an attempt is made to connect to the local host on port 4433.

=item B<-cert certname>

The certificate to use, if one is requested by the server. The default is
not to use a certificate.

D
PR: 910  
Dr. Stephen Henson 已提交
63 64 65 66
=item B<-certform format>

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

67 68 69 70 71
=item B<-key keyfile>

The private key to use. If not specified then the certificate file will
be used.

D
PR: 910  
Dr. Stephen Henson 已提交
72 73 74 75 76 77 78 79 80
=item B<-keyform format>

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

=item B<-pass arg>

the private key password source. For more information about the format of B<arg>
see the B<PASS PHRASE ARGUMENTS> section in L<openssl(1)|openssl(1)>.

81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132
=item B<-verify depth>

The verify depth to use. This specifies the maximum length of the
server certificate chain and turns on server certificate verification.
Currently the verify operation continues after errors so all the problems
with a certificate chain can be seen. As a side effect the connection
will never fail due to a server certificate verify failure.

=item B<-CApath directory>

The directory to use for server certificate verification. This directory
must be in "hash format", see B<verify> for more information. These are
also used when building the client certificate chain.

=item B<-CAfile file>

A file containing trusted certificates to use during server authentication
and to use when attempting to build the client certificate chain.

=item B<-reconnect>

reconnects to the same server 5 times using the same session ID, this can
be used as a test that session caching is working.

=item B<-pause>

pauses 1 second between each read and write call.

=item B<-showcerts>

display the whole server certificate chain: normally only the server
certificate itself is displayed.

=item B<-prexit>

print session information when the program exits. This will always attempt
to print out information even if the connection fails. Normally information
will only be printed out once if the connection succeeds. This option is useful
because the cipher in use may be renegotiated or the connection may fail
because a client certificate is required or is requested only after an
attempt is made to access a certain URL. Note: the output produced by this
option is not always accurate because a connection might never have been
established.

=item B<-state>

prints out the SSL session states.

=item B<-debug>

print extensive debugging information including a hex dump of all traffic.

B
Bodo Möller 已提交
133 134 135 136
=item B<-msg>

show all protocol messages with hex dump.

137 138
=item B<-nbio_test>

U
Ulf Möller 已提交
139
tests non-blocking I/O
140 141 142

=item B<-nbio>

U
Ulf Möller 已提交
143
turns on non-blocking I/O
144 145 146 147 148 149

=item B<-crlf>

this option translated a line feed from the terminal into CR+LF as required
by some servers.

150 151 152 153 154
=item B<-ign_eof>

inhibit shutting down the connection when end of file is reached in the
input.

155 156
=item B<-quiet>

U
ispell  
Ulf Möller 已提交
157
inhibit printing of session and certificate information.  This implicitly
158
turns on B<-ign_eof> as well.
159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177

=item B<-ssl2>, B<-ssl3>, B<-tls1>, B<-no_ssl2>, B<-no_ssl3>, B<-no_tls1>

these options disable the use of certain SSL or TLS protocols. By default
the initial handshake uses a method which should be compatible with all
servers and permit them to use SSL v3, SSL v2 or TLS as appropriate.

Unfortunately there are a lot of ancient and broken servers in use which
cannot handle this technique and will fail to connect. Some servers only
work if TLS is turned off with the B<-no_tls> option others will only
support SSL v2 and may need the B<-ssl2> option.

=item B<-bugs>

there are several known bug in SSL and TLS implementations. Adding this
option enables various workarounds.

=item B<-cipher cipherlist>

178 179 180 181
this allows the cipher list sent by the client to be modified. Although
the server determines which cipher suite is used it should take the first
supported cipher in the list sent by the client. See the B<ciphers>
command for more information.
182

183 184 185 186
=item B<-starttls protocol>

send the protocol-specific message(s) to switch to TLS for communication.
B<protocol> is a keyword for the intended protocol.  Currently, the only
187
supported keywords are "smtp" and "pop3".
188

189 190 191 192 193 194 195
=item B<-engine id>

specifying an engine (by it's unique B<id> string) will cause B<s_client>
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.

196 197 198 199 200 201 202 203
=item B<-rand file(s)>

a file or files containing random data used to seed the random number
generator, or an EGD socket (see L<RAND_egd(3)|RAND_egd(3)>).
Multiple files can be specified separated by a OS-dependent character.
The separator is B<;> for MS-Windows, B<,> for OpenVMS, and B<:> for
all others.

U
Ulf Möller 已提交
204 205
=back

206 207 208 209
=head1 CONNECTED COMMANDS

If a connection is established with an SSL server then any data received
from the server is displayed and any key presses will be sent to the
210
server. When used interactively (which means neither B<-quiet> nor B<-ign_eof>
U
ispell  
Ulf Möller 已提交
211
have been given), the session will be renegotiated if the line begins with an
212 213
B<R>, and if the line begins with a B<Q> or if end of file is reached, the
connection will be closed down.
214 215 216 217 218 219 220 221 222 223 224 225 226

=head1 NOTES

B<s_client> can be used to debug SSL servers. To connect to an SSL HTTP
server the command:

 openssl s_client -connect servername:443

would typically be used (https uses port 443). If the connection succeeds
then an HTTP command can be given such as "GET /" to retrieve a web page.

If the handshake fails then there are several possible causes, if it is
nothing obvious like no client certificate then the B<-bugs>, B<-ssl2>,
L
Lutz Jänicke 已提交
227
B<-ssl3>, B<-tls1>, B<-no_ssl2>, B<-no_ssl3>, B<-no_tls1> options can be tried
228 229 230 231 232 233 234 235 236 237
in case it is a buggy server. In particular you should play with these
options B<before> submitting a bug report to an OpenSSL mailing list.

A frequent problem when attempting to get client certificates working
is that a web client complains it has no certificates or gives an empty
list to choose from. This is normally because the server is not sending
the clients certificate authority in its "acceptable CA list" when it
requests a certificate. By using B<s_client> the CA list can be viewed
and checked. However some servers only request client authentication
after a specific URL is requested. To obtain the list in this case it
L
Lutz Jänicke 已提交
238
is necessary to use the B<-prexit> option and send an HTTP request
239 240 241 242 243 244 245 246 247 248 249 250 251
for an appropriate page.

If a certificate is specified on the command line using the B<-cert>
option it will not be used unless the server specifically requests
a client certificate. Therefor merely including a client certificate
on the command line is no guarantee that the certificate works.

If there are problems verifying a server certificate then the
B<-showcerts> option can be used to show the whole chain.

=head1 BUGS

Because this program has a lot of options and also because some of
D
Dr. Stephen Henson 已提交
252
the techniques used are rather old, the C source of s_client is rather
253 254 255 256 257 258 259 260 261 262 263
hard to read and not a model of how things should be done. A typical
SSL client program would be much simpler.

The B<-verify> option should really exit if the server verification
fails.

The B<-prexit> option is a bit of a hack. We should really report
information whenever a session is renegotiated.

=head1 SEE ALSO

264
L<sess_id(1)|sess_id(1)>, L<s_server(1)|s_server(1)>, L<ciphers(1)|ciphers(1)>
265 266

=cut