aboutsummaryrefslogtreecommitdiff
path: root/UPGRADE
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2002-09-25 16:20:29 +0000
committerDaniel Stenberg <daniel@haxx.se>2002-09-25 16:20:29 +0000
commit9031e33b66bcc9f1fb51a3e7542904110429d442 (patch)
tree2f39609a0993930ed2bbc06c0789d0ab5e4d99c5 /UPGRADE
parent1ee1f5f427bf39f07f11db812c0a62406a56bffa (diff)
language!
Diffstat (limited to 'UPGRADE')
-rw-r--r--UPGRADE10
1 files changed, 5 insertions, 5 deletions
diff --git a/UPGRADE b/UPGRADE
index 38d9679c5..c5e36c26b 100644
--- a/UPGRADE
+++ b/UPGRADE
@@ -3,12 +3,12 @@ Upgrading to curl/libcurl 7.10 from any previous version
libcurl 7.10 performs peer SSL certificate verification by default. This is
done by installing a default CA cert bundle on 'make install' (or similar),
-that is used by default on operations against SSL servers.
+that CA bundle package is used by default on operations against SSL servers.
-Alas, if you use communicate with HTTPS servers using certifcates that are
-signed by CAs present in the bundle, you will not notice and changed behavior
-and you will seeminglessly get a higher security level on your SSL connections
-since you will make sure that the remote server really is who it claims to be.
+Alas, if you communicate with HTTPS servers using certifcates that are signed
+by CAs present in the bundle, you will not notice any changed behavior and you
+will seeminglessly get a higher security level on your SSL connections since
+can be sure that the remote server really is the one it claims to be.
If the remote server uses a self-signed certificate, or if you don't install
curl's CA cert bundle or if it uses a certificate signed by a CA that isn't