Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Consider adding cacert (aside capath) #17

Closed
zoldar opened this issue Oct 13, 2015 · 1 comment
Closed

Consider adding cacert (aside capath) #17

zoldar opened this issue Oct 13, 2015 · 1 comment

Comments

@zoldar
Copy link
Contributor

zoldar commented Oct 13, 2015

From a short research I just did, capath (or in libcurl's terms, CURLOPT_CAPATH) will be rarely the thing that the library user actually wants. The usual use case of using such option is in case of a self-signed certificate.

The problem is, CURLOPT_CAPATH is expected to be a directory containing CA certificate files along with their hashes. Typically, the user will want to provide just a single CA certificate file. I suggest adding another option, cacert, which will translate to CURLOPT_CAINFO, which is an option that supports just that scenario.

I can prepare a PR for that if that addition will get settled.
@puzza007
Copy link
Owner

Sounds good 👍

@zoldar zoldar mentioned this issue Oct 15, 2015
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@puzza007 @zoldar