<![CDATA[wolfSSL - Embedded SSL Library — haproxy]]> https://www.wolfssl.com/forums/topic1329-haproxy.html Tue, 12 Mar 2019 22:38:27 +0000 PunBB <![CDATA[Re: haproxy]]> https://www.wolfssl.com/forums/post4484.html#p4484 Hi gaconvn1106,

As mentioned on issue #1335:

wolfSSL maintains a custom port to haproxy, if you email us at support@wolfssl.com or use the zendesk portal at https://wolfssl.zendesk.com we should be able to get you an evaluation version of our port.

We are happy to assist any users via github issues or here on the forums but our engineers utilize zendesk mainly and are more responsive via the official support channel. If you ever notice delayed response times in github or here on the forums please use support@wolfssl.com or the zendesk portal to move your issue forward in a more expedient manner!

Regards,

K

]]> Tue, 12 Mar 2019 22:38:27 +0000 https://www.wolfssl.com/forums/post4484.html#p4484 <![CDATA[haproxy]]> https://www.wolfssl.com/forums/post4470.html#p4470 The issue #1335 is closed but I can't find a answer there if wolfssl is a possible TLS/SSL library for haproxy.

As I build haproxy with openssl and boringssl I'm courious if wolfssl is also a possible TLS/SSL library for haproxy, not only technically also from license point of view.

These are the image which I maintain.
https://hub.docker.com/r/me2digital/haproxy19
https://hub.docker.com/r/me2digital/hap … -boringssl

]]> Thu, 21 Feb 2019 03:18:28 +0000 https://www.wolfssl.com/forums/post4470.html#p4470