'M-x ispell-buffer'

This commit is contained in:
Daniel Stenberg 2004-06-29 13:16:30 +00:00
parent 03f8ec89db
commit d4b0999415
1 changed files with 5 additions and 5 deletions

View File

@ -13,8 +13,8 @@ can be sure that the remote server really is the one it claims to be.
If the remote server uses a self-signed certificate, if you don't install If the remote server uses a self-signed certificate, if you don't install
curl's CA cert bundle, if the server uses a certificate signed by a CA that curl's CA cert bundle, if the server uses a certificate signed by a CA that
isn't included in the bundle or if the remoste host is an imposter isn't included in the bundle or if the remote host is an impostor
impersonating your favourite site, and you want to transfer files from this impersonating your favorite site, and you want to transfer files from this
server, do one of the following: server, do one of the following:
1. Tell libcurl to *not* verify the peer. With libcurl you disable with with 1. Tell libcurl to *not* verify the peer. With libcurl you disable with with
@ -38,7 +38,7 @@ server, do one of the following:
cert path by setting the environment variable CURL_CA_BUNDLE to the path cert path by setting the environment variable CURL_CA_BUNDLE to the path
of your choice. of your choice.
If you're using the curl command line toll on Windows, curl will search If you're using the curl command line tool on Windows, curl will search
for a CA cert file named "curl-ca-bundle.crt" in these directories and in for a CA cert file named "curl-ca-bundle.crt" in these directories and in
this order: this order:
1. application's directory 1. application's directory
@ -47,8 +47,8 @@ server, do one of the following:
4. Windows Directory (e.g. C:\windows) 4. Windows Directory (e.g. C:\windows)
5. all directories along %PATH% 5. all directories along %PATH%
Neglecting to use one of the above menthods when dealing with a server using a Neglecting to use one of the above methods when dealing with a server using a
certficate that isn't signed by one of the certficates in the installed CA certificate that isn't signed by one of the certificates in the installed CA
cert bundle, will cause SSL to report an error ("certificate verify failed") cert bundle, will cause SSL to report an error ("certificate verify failed")
during the handshake and SSL will then refuse further communication with that during the handshake and SSL will then refuse further communication with that
server. server.