Import OpenSSL 1.1.1i
This commit is contained in:
@@ -427,11 +427,11 @@ File to send output of B<-msg> or B<-trace> to, default standard output.
|
||||
|
||||
=item B<-nbio_test>
|
||||
|
||||
Tests non-blocking I/O
|
||||
Tests nonblocking I/O
|
||||
|
||||
=item B<-nbio>
|
||||
|
||||
Turns on non-blocking I/O
|
||||
Turns on nonblocking I/O
|
||||
|
||||
=item B<-crlf>
|
||||
|
||||
@@ -781,14 +781,14 @@ 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
|
||||
and checked. However, some servers only request client authentication
|
||||
after a specific URL is requested. To obtain the list in this case it
|
||||
is necessary to use the B<-prexit> option and send an HTTP request
|
||||
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
|
||||
a client certificate. Therefore, 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
|
||||
|
||||
Reference in New Issue
Block a user