FreeBSD Manual Pages
CURLOPT_PR...EDPUBLICKEY(3) Library Functions Manual CURLOPT_PR...EDPUBLICKEY(3) NAME CURLOPT_PROXY_PINNEDPUBLICKEY - pinned public key for https proxy SYNOPSIS #include <curl/curl.h> CURLcode curl_easy_setopt(CURL *handle, CURLOPT_PROXY_PINNEDPUBLICKEY, char *pinnedpubkey); DESCRIPTION Pass a pointer to a null-terminated string as parameter. The string can be the filename of your pinned public key. The file format expected is "PEM" or "DER". The string can also be any number of base64 encoded sha256 hashes preceded by "sha256//" and separated by ";" When negotiating a TLS or SSL connection, the https proxy sends a certifi- cate indicating its identity. A public key is extracted from this certifi- cate and if it does not exactly match the public key provided to this op- tion, libcurl aborts the connection before sending or receiving any data. On mismatch, CURLE_SSL_PINNEDPUBKEYNOTMATCH is returned. The application does not have to keep the string around after setting this option. Using this option multiple times makes the last set string override the previous ones. Set it to NULL to disable its use again. DEFAULT NULL PROTOCOLS This functionality affects all TLS based protocols: HTTPS, FTPS, IMAPS, POP3S, SMTPS etc. This option works only with the following TLS backends: GnuTLS, OpenSSL, mbedTLS and wolfSSL EXAMPLE int main(void) { CURL *curl = curl_easy_init(); if(curl) { CURLcode result; curl_easy_setopt(curl, CURLOPT_URL, "https://example.com"); curl_easy_setopt(curl, CURLOPT_PROXY, "https://proxy.example:443"); curl_easy_setopt(curl, CURLOPT_PROXY_PINNEDPUBLICKEY, "sha256//YhKJKSzoTt2b5FP18fvpHo7fJYqQCjA" "a3HWY3tvRMwE=;sha256//t62CeU2tQiqkexU74" "Gxa2eg7fRbEgoChTociMee9wno="); /* Perform the request */ result = curl_easy_perform(curl); curl_easy_cleanup(curl); } } PUBLIC KEY EXTRACTION If you do not have the https proxy server's public key file you can extract it from the https proxy server's certificate. # retrieve the server's certificate if you do not already have it # # be sure to examine the certificate to see if it is what you expected # # Windows-specific: # - Use NUL instead of /dev/null. # - OpenSSL may wait for input instead of disconnecting. Hit enter. # - If you do not have sed, then copy the certificate into a file: # Lines from -----BEGIN CERTIFICATE----- to -----END CERTIFICATE-----. # openssl s_client -servername www.example.com -connect www.example.com:443 \ < /dev/null | sed -n "/-----BEGIN/,/-----END/p" > www.example.com.pem # extract public key in pem format from certificate openssl x509 -in www.example.com.pem -pubkey -noout > www.example.com.pubkey.pem # convert public key from pem to der openssl asn1parse -noout -inform pem -in www.example.com.pubkey.pem \ -out www.example.com.pubkey.der # sha256 hash and base64 encode der to string for use openssl dgst -sha256 -binary www.example.com.pubkey.der | openssl base64 The public key in PEM format contains a header, base64 data and a footer: -----BEGIN PUBLIC KEY----- [BASE 64 DATA] -----END PUBLIC KEY----- HISTORY PEM/DER support: 7.52.0: GnuTLS, OpenSSL, mbedTLS, wolfSSL sha256 support: 7.52.0: GnuTLS, OpenSSL, mbedTLS, wolfSSL Other SSL backends not supported. AVAILABILITY Added in curl 7.52.0 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). SEE ALSO CURLOPT_PINNEDPUBLICKEY(3), CURLOPT_PROXY_CAINFO(3), CURLOPT_PROXY_CAP- ATH(3), CURLOPT_PROXY_SSL_VERIFYHOST(3), CURLOPT_PROXY_SSL_VERIFYPEER(3) libcurl 2026-06-11 CURLOPT_PR...EDPUBLICKEY(3)
NAME | SYNOPSIS | DESCRIPTION | DEFAULT | PROTOCOLS | EXAMPLE | PUBLIC KEY EXTRACTION | HISTORY | AVAILABILITY | RETURN VALUE | SEE ALSO
Want to link to this manual page? Use this URL:
<https://man.freebsd.org/cgi/man.cgi?query=CURLOPT_PROXY_PINNEDPUBLICKEY&sektion=3&manpath=FreeBSD+Ports+15.1.quarterly>