Feature #2353
openLoad certificate and private key from a X509 object and EVP_PKEY object
0%
Description
At this point WT can only load a certificate and a private key from files. This is not enough for me. I want to be able to load the certificate and private key from the another source. Let's say Windows Certificate Store. Using Openssl CAPI engine one could obtain a pointer to a X509 for certificate and a pointer to EVP_PKEY for private key from the Certificate Store. These could be passed down to WT and initialize the SSL context. In this scenario there will not be a need for a SSL password callback function.
I added a rough patch with my modifications based on WT 3.3.0. Any suggestions are welcomed.
Files
Updated by Wim Dumon about 11 years ago
- Status changed from New to Feedback
- Assignee set to Wim Dumon
Hi,
Not so long ago I ran into the issue that we should also load the list of trusted root certificates from the certificate store on Windows (for http client). I will take a look at your patch when I add that feature to Wt.
BR,
Wim.