From b47c17d67c9b5c9e985375b090f0140bf43cb146 Mon Sep 17 00:00:00 2001 From: Kamil Dudka Date: Wed, 25 Mar 2015 13:48:41 +0100 Subject: nss: implement public key pinning for NSS backend Bug: https://bugzilla.redhat.com/1195771 --- docs/curl.1 | 3 ++- docs/libcurl/opts/CURLOPT_PINNEDPUBLICKEY.3 | 2 +- 2 files changed, 3 insertions(+), 2 deletions(-) (limited to 'docs') diff --git a/docs/curl.1 b/docs/curl.1 index 908f64899..0e567159e 100644 --- a/docs/curl.1 +++ b/docs/curl.1 @@ -548,7 +548,8 @@ 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 will abort the connection before sending or receiving any data. -This is currently only implemented in the OpenSSL, GnuTLS and GSKit backends. +This is currently only implemented in the OpenSSL, GnuTLS, NSS and GSKit +backends. If this option is used several times, the last one will be used. (Added in 7.39.0) diff --git a/docs/libcurl/opts/CURLOPT_PINNEDPUBLICKEY.3 b/docs/libcurl/opts/CURLOPT_PINNEDPUBLICKEY.3 index 2d8639275..4cc68b1d3 100644 --- a/docs/libcurl/opts/CURLOPT_PINNEDPUBLICKEY.3 +++ b/docs/libcurl/opts/CURLOPT_PINNEDPUBLICKEY.3 @@ -52,7 +52,7 @@ if(curl) { .fi .SH AVAILABILITY If built TLS enabled. This is currently only implemented in the OpenSSL, -GnuTLS and GSKit backends. +GnuTLS, NSS and GSKit backends. Added in libcurl 7.39.0 .SH RETURN VALUE -- cgit v1.2.3