curl / Mailing Lists / curl-library / Single Mail
Buy commercial curl support from WolfSSL. We help you work out your issues, debug your libcurl applications, use the API, port to new platforms, add new features and more. With a team lead by the curl founder himself.

Feature request: passing ssl certificate and/or key parameter as content, not path

From: Nicolas Mora via curl-library <>
Date: Thu, 10 Oct 2019 10:48:46 -0400


According to the libcurl documentation [1], if you want to specify a SSL
certificate or key to the connection, the parameter must be a file path
rather than the certificate or key value: "Pass a pointer to a zero
terminated string as parameter. The string should be the file name of
your client certificate."

This makes it difficult to use ssl authenticated requests on an embedded
program where those options can come from various places (API response,
config file, self-generated, whatever). The only workaround I find is to
use mkstemp, which adds layers of complexity.

Would it be possible to add the possibility to pass the cert/key content
as well? By adding a new value to CURLOPT_SSLCERTTYPE for example, like

I can work on a patch but I'd like to know first if the idea would be


[1] -
Received on 2019-10-10