mirror of
https://github.com/curl/curl.git
synced 2026-08-26 01:23:32 +03:00
docs: explain how PINNEDPUBLICKEY is independent of VERIFYPEER
- Explain that peer verification via CURLOPT_PINNEDPUBLICKEY takes place even if peer verification via CURLOPT_SSL_VERIFYPEER is turned off. The behavior is verified by test2048. Bug: https://github.com/curl/curl/issues/2935#issuecomment-418371872 Reported-by: claudiusaiz@users.noreply.github.com Bug: https://github.com/curl/curl/discussions/11910 Reported-by: Hakan Sunay Halil Closes https://github.com/curl/curl/pull/11930
This commit is contained in:
parent
34cdcb9b96
commit
398c59ae63
2 changed files with 12 additions and 3 deletions
|
|
@ -43,6 +43,9 @@ indicating its identity. A public key is extracted from this certificate and
|
|||
if it does not exactly match the public key provided to this option, curl
|
||||
aborts the connection before sending or receiving any data.
|
||||
|
||||
This option is independent of option \fICURLOPT_SSL_VERIFYPEER(3)\fP. If you
|
||||
turn off that option then the peer is still verified by public key.
|
||||
|
||||
On mismatch, \fICURLE_SSL_PINNEDPUBKEYNOTMATCH\fP is returned.
|
||||
|
||||
The application does not have to keep the string around after setting this
|
||||
|
|
@ -118,7 +121,7 @@ sha256 support:
|
|||
|
||||
7.54.1: Secure Transport on macOS 10.7+/iOS 10+
|
||||
|
||||
7.58.1: Schannel Windows XP SP3+
|
||||
7.58.1: Schannel
|
||||
|
||||
Other SSL backends not supported.
|
||||
.SH RETURN VALUE
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue