mojave man page for curlopt_sslkey

Query: curlopt_sslkey

OS: mojave

Section: 3

Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar

CURLOPT_SSLKEY(3)					     curl_easy_setopt options						 CURLOPT_SSLKEY(3)

NAME
CURLOPT_SSLKEY - specify private keyfile for TLS and SSL client cert
SYNOPSIS
#include <curl/curl.h> CURLcode curl_easy_setopt(CURL *handle, CURLOPT_SSLKEY, char *keyfile);
DESCRIPTION
Pass a pointer to a zero terminated string as parameter. The string should be the file name of your private key. The default format is "PEM" and can be changed with CURLOPT_SSLKEYTYPE(3). (iOS and Mac OS X only) This option is ignored if curl was built against Secure Transport. Secure Transport expects the private key to be already present in the keychain or PKCS#12 file containing the certificate. The application does not have to keep the string around after setting this option.
DEFAULT
NULL
PROTOCOLS
All TLS based protocols: HTTPS, FTPS, IMAPS, POP3S, SMTPS etc.
EXAMPLE
TODO
AVAILABILITY
If built TLS enabled.
RETURN VALUE
Returns CURLE_OK if TLS is supported, CURLE_UNKNOWN_OPTION if not, or CURLE_OUT_OF_MEMORY if there was insufficient heap space.
SEE ALSO
CURLOPT_SSLKEYTYPE(3), CURLOPT_SSLCERT(3), libcurl 7.54.0 December 21, 2016 CURLOPT_SSLKEY(3)
Related Man Pages
curlopt_cainfo(3) - mojave
curlopt_proxy_sslcert(3) - mojave
curlopt_sslcert(3) - mojave
curlopt_sslkey(3) - mojave
curlopt_tlsauth_password(3) - mojave
Similar Topics in the Unix Linux Community
Trustix Secure Linux Security Advisory - bind, clamav, curl ... - Help Net Security
Microsoft Security Advisory (977377): Vulnerability in TLS/SSL Could Allow Spoofing - 2/9/2010
Implicit FTPS error on Citrix Sharefile