Artifactspublic-v0

curl

master
ply4 git calls437 ms288 KiB2 cachedprotocol v2
108 lines3.3 KiBRaw

NAME

CURLOPT_SSL_VERIFYPEER - verify the peer's SSL certificate

SYNOPSIS

c
#include <curl/curl.h>

CURLcode curl_easy_setopt(CURL *handle, CURLOPT_SSL_VERIFYPEER, long verify);

DESCRIPTION

Pass a long as parameter to enable or disable.

This option determines whether curl verifies the authenticity of the peer's certificate. A value of 1 means curl verifies; 0 (zero) means it does not.

When negotiating a TLS or SSL connection, the server sends a certificate indicating its identity. curl verifies whether the certificate is authentic, i.e. that you can trust that the server is who the certificate says it is. This trust is based on a chain of digital signatures, rooted in certification authority (CA) certificates you supply. curl uses a default bundle of CA certificates (the path for that is determined at build time) and you can specify alternate certificates with the CURLOPT_CAINFO(3) option or the CURLOPT_CAPATH(3) option.

When CURLOPT_SSL_VERIFYPEER(3) is enabled, and the verification fails to prove that the certificate is signed by a CA, the connection fails.

When this option is disabled (set to zero), the CA certificates are not loaded and the peer certificate verification is skipped.

Authenticating the certificate is not enough to be sure about the server. You typically also want to ensure that the server is the server you mean to be talking to. Use CURLOPT_SSL_VERIFYHOST(3) for that. The check that the host name in the certificate is valid for the hostname you are connecting to is done independently of the CURLOPT_SSL_VERIFYPEER(3) option.

WARNING: disabling verification of the certificate allows bad guys to man-in-the-middle the communication without you knowing it. Disabling verification makes the communication insecure. Having encryption on a transfer is not enough as you cannot be sure that you are communicating with the correct end-point.

When libcurl uses secure protocols it trusts responses and allows for example HSTS and Alt-Svc information to be stored and used subsequently. Disabling certificate verification can make libcurl trust and use such information from malicious servers.

For LDAP, this option is supported when using the OpenLDAP backend, and with the WinLDAP backend since 8.22.0. With AppleLDAP, the certificate chain is still verified when this option is disabled.

DEFAULT

1 - enabled

%PROTOCOLS%

EXAMPLE

c
int main(void)
{
  CURL *curl = curl_easy_init();
  if(curl) {
    CURLcode result;
    curl_easy_setopt(curl, CURLOPT_URL, "https://example.com");

    /* Set the default value: strict certificate check please */
    curl_easy_setopt(curl, CURLOPT_SSL_VERIFYPEER, 1L);

    result = curl_easy_perform(curl);
    curl_easy_cleanup(curl);
  }
}

%AVAILABILITY%

RETURN VALUE

curl_easy_setopt(3) returns a CURLcode indicating success or error.

CURLE_OK (0) means everything was OK, non-zero means an error occurred, see libcurl-errors(3).

1---
2c: Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
3SPDX-License-Identifier: curl
4Title: CURLOPT_SSL_VERIFYPEER
5Section: 3
6Source: libcurl
7See-also:
8 - CURLINFO_CAINFO (3)
9 - CURLINFO_CAPATH (3)
10 - CURLOPT_CAINFO (3)
11 - CURLOPT_PROXY_SSL_VERIFYHOST (3)
12 - CURLOPT_PROXY_SSL_VERIFYPEER (3)
13 - CURLOPT_SSL_VERIFYHOST (3)
14Protocol:
15 - TLS
16TLS-backend:
17 - All
18Added-in: 7.4.2
19---
21# NAME
23CURLOPT_SSL_VERIFYPEER - verify the peer's SSL certificate
25# SYNOPSIS
27~~~c
28#include <curl/curl.h>
30CURLcode curl_easy_setopt(CURL *handle, CURLOPT_SSL_VERIFYPEER, long verify);
31~~~
33# DESCRIPTION
35Pass a long as parameter to enable or disable.
37This option determines whether curl verifies the authenticity of the peer's
38certificate. A value of 1 means curl verifies; 0 (zero) means it does not.
40When negotiating a TLS or SSL connection, the server sends a certificate
41indicating its identity. curl verifies whether the certificate is authentic,
42i.e. that you can trust that the server is who the certificate says it is.
43This trust is based on a chain of digital signatures, rooted in certification
44authority (CA) certificates you supply. curl uses a default bundle of CA
45certificates (the path for that is determined at build time) and you can
46specify alternate certificates with the CURLOPT_CAINFO(3) option or the
47CURLOPT_CAPATH(3) option.
49When CURLOPT_SSL_VERIFYPEER(3) is enabled, and the verification fails to
50prove that the certificate is signed by a CA, the connection fails.
52When this option is disabled (set to zero), the CA certificates are not loaded
53and the peer certificate verification is skipped.
55Authenticating the certificate is not enough to be sure about the server. You
56typically also want to ensure that the server is the server you mean to be
57talking to. Use CURLOPT_SSL_VERIFYHOST(3) for that. The check that the host
58name in the certificate is valid for the hostname you are connecting to is
59done independently of the CURLOPT_SSL_VERIFYPEER(3) option.
61**WARNING:** disabling verification of the certificate allows bad guys to
62man-in-the-middle the communication without you knowing it. Disabling
63verification makes the communication insecure. Having encryption on a transfer
64is not enough as you cannot be sure that you are communicating with the
65correct end-point.
67When libcurl uses secure protocols it trusts responses and allows for example
68HSTS and Alt-Svc information to be stored and used subsequently. Disabling
69certificate verification can make libcurl trust and use such information from
70malicious servers.
72For LDAP, this option is supported when using the OpenLDAP backend, and with
73the WinLDAP backend since 8.22.0. With AppleLDAP, the certificate chain is
74still verified when this option is disabled.
76# DEFAULT
781 - enabled
80# %PROTOCOLS%
82# EXAMPLE
84~~~c
85int main(void)
87 CURL *curl = curl_easy_init();
88 if(curl) {
89 CURLcode result;
90 curl_easy_setopt(curl, CURLOPT_URL, "https://example.com");
92 /* Set the default value: strict certificate check please */
93 curl_easy_setopt(curl, CURLOPT_SSL_VERIFYPEER, 1L);
95 result = curl_easy_perform(curl);
96 curl_easy_cleanup(curl);
97 }
99~~~
101# %AVAILABILITY%
103# RETURN VALUE
105curl_easy_setopt(3) returns a CURLcode indicating success or error.
107CURLE_OK (0) means everything was OK, non-zero means an error occurred, see
108libcurl-errors(3).
Diagnostics4 git calls · 437 ms
CallStatusSizeTime0437 ms
discover200152 B3 ms
git.upload-pack discover
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=2
git.response.bytes=152
git.server.agent=gitty/1.0
git.server.object_format=sha1
git.server.caps=agent ls-refs fetch object-format
git.server.fetch=shallow filter sideband-all
git.protocol.version=2
git.pkt.frames=8
git.pkt.data=6
git.pkt.flush=2
git.pkt.delim=0
git.pkt.bytes=152
git.pkt.payload.max=34
ls-refs200149 B · hit3 ms
git.upload-pack ls-refs
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=ls-refs
git.upstream.dur_ms=3
git.response.bytes=149
git.response.cache=HIT
git.response.duration_ms=3
git.protocol.version=2
git.pkt.frames=3
git.pkt.data=2
git.pkt.flush=1
git.pkt.delim=0
git.pkt.bytes=149
git.pkt.payload.max=78
git.ls_refs.count=2
git.ls_refs.head=refs/heads/master
fetchblob:none · deepen 10200287 KiB · hit2 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=432
git.response.bytes=293470
git.response.cache=HIT
git.response.duration_ms=2
git.fetch.filter=blob:none
git.fetch.filter.requested=tree:0
git.fetch.filter.fallback=blob:none
git.fetch.filter.learned=false
git.fetch.wants=31c911efe5652725e930f4d2e60c9060e5f6646d
git.fetch.haves.count=0
git.fetch.deepen=10
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=10
git.pkt.data=8
git.pkt.flush=1
git.pkt.delim=1
git.pkt.bytes=293470
git.pkt.payload.max=65516
git.sideband.band1.bytes=293354
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0
git.pack.objects=87
git.pack.bytes=293354
git.pack.ofs_delta=0
git.pack.ref_delta=1
git.pack.chain.max=1
git.pack.trailer=6a646bcda6740bab42e321b51998b52ea15146c0
git.pack.full=86
Open pack map
fetch2001.6 KiB432 ms
git.upload-pack fetch
http.response.status_code=200
git.response.bytes=1613
git.response.cache=MISS
git.response.duration_ms=432
git.fetch.wants=8d4a1b3aca0373f118a1f3397c61bf9a88c14e55
git.fetch.haves.count=0
git.fetch.deepen=0
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=3
git.pkt.data=2
git.pkt.flush=1
git.pkt.delim=0
git.pkt.bytes=1613
git.pkt.payload.max=1592
git.sideband.band1.bytes=1591
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0

Each row is one HTTP round trip ply made to the git server for this page, on one timeline. discover asks what the server speaks, ls-refs lists branch tips, fetch brings objects by id. A hit was served by Workers Cache. Tap a row for its wire details.

Remote
https://5ad2236b39de4c8bd8f6270ea63f3ea9.artifacts.cloudflare.net/git/public-v0/curl.git
Ref
refs/heads/master
Commit
31c911efe5652725e930f4d2e60c9060e5f6646d
cf-ray
a5e362888a05b23b
Request
4767f514…
Protocol
v2 · sha1
Agent
gitty/1.0
Filter
advertised
Fetch
shallow filter sideband-all
Capabilities
agent ls-refs fetch object-format