Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
T
TLMSP curl
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
CYBER - Cyber Security
TS 103 523 MSP
TLMSP
TLMSP curl
Commits
9031e33b
Commit
9031e33b
authored
22 years ago
by
Daniel Stenberg
Browse files
Options
Downloads
Patches
Plain Diff
language!
parent
1ee1f5f4
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
UPGRADE
+5
-5
5 additions, 5 deletions
UPGRADE
with
5 additions
and
5 deletions
UPGRADE
+
5
−
5
View file @
9031e33b
...
...
@@ -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 an
d
changed behavior
and you
will seeminglessly get a higher security level on your SSL connections
since you will mak
e 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 an
y
changed behavior
and you
will seeminglessly get a higher security level on your SSL connections
since
can b
e 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
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment