[Libwebsockets] client cert path

Joel Winarske joel.winarske at gmail.com
Tue Feb 21 05:56:23 CET 2017


PR #807

On Mon, Feb 20, 2017 at 5:04 PM, Andy Green <andy at warmcat.com> wrote:

>
>
> On 02/19/2017 02:33 AM, Joel Winarske wrote:
>
>> I hacked it up for now, and added support for the following lwsws
>> parameters:
>>
>> "client-ssl-ca"
>> "client-ssl-cert"
>> "client-ssl-key"
>> "client-ssl-ciphers"
>>
>
> Can you send me a patch for this?
>
> It will save me some time.
>
> -Andy
>
>
>> Cheers
>>
>> On Thu, Feb 16, 2017 at 8:19 PM, Andy Green <andy at warmcat.com <mailto:
>> andy at warmcat.com>> wrote:
>>
>>
>>
>>     On 17 February 2017 11:45:09 GMT+08:00, Joel Winarske
>>     <joel.winarske at gmail.com <mailto:joel.winarske at gmail.com>> wrote:
>>     >When using the client to connect to https, and the vhost is not
>>     >configured
>>     >with certs, what cert path is used?
>>
>>     Without lwsws actually the user code can control it when it calls
>>     lws_init_vhost_client_ssl(), it can prepare the client
>>     cert-related members in the context / vhost creation info it
>>     passes in appropriately for the client cert init.
>>
>>     With lwsws it needs more conf and I don't have time to do it right
>>     now.
>>
>>     You can simulate it by hacking lws_init_vhost_client_ssl()
>>     (context.c) to set the info members there by hand for now. I'll
>>     stitch the conf support in later.
>>
>>     -Andy
>>
>>     >
>>     >Thanks,
>>     >Joel
>>
>>     --
>>     Sent from my Android device with K-9 Mail. Please excuse my brevity.
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://libwebsockets.org/pipermail/libwebsockets/attachments/20170220/31fec766/attachment-0002.html>


More information about the Libwebsockets mailing list