Hi Lukas,
On Thu, 22 Nov 2018 19:39:11 +0100
Lukas Tribus wrote:
> Trying to understand the use-case better here, binding to any IP is
> not acceptable? Your client *needs* to bind to specific IPs?
one bind for multiple IPs would reduce the flexibility of the config, you could
not longer set
Hi again,
of course i forgot to attach the patch...
Kind regards,
Julian
diff --git a/include/types/ssl_sock.h b/include/types/ssl_sock.h
index 2e02631c..76073f37 100644
--- a/include/types/ssl_sock.h
+++ b/include/types/ssl_sock.h
@@ -71,4 +71,14 @@ struct sh_ssl_sess_hdr {
unsigned char
Hello,
one of our clients runs a haproxy setup with a 2000+ SSL-Certificates on
multiple IPs. As an OpenSSL CTX needs to be created for each certificate for
each sockets, restarting or reloading the config takes several minutes.
Therfore i like to propose to share the CTX for on multiple
3 matches
Mail list logo