jimmy wrote:
Hi,
I am trying to write an http server which supports virtual servers &
ssl sessions. If I were to support the TLS 1.0 server name extension
(which says different virtual servers cud send different
certificates), then would I be able to use the same SSL_CTX across the
different
jimmy wrote:
Peter Sylvester wrote:
It happened that I played with this a bit.
It is not just that you have a list of servers in one context, all
parameters of the server e;g. requirements for user certs etc can be
different, so a separate SSL_CTX seems useful.
does this theoretically rule o
Peter Sylvester wrote:
> It happened that I played with this a bit.
>
> It is not just that you have a list of servers in one context, all
> parameters of the server e;g. requirements for user certs etc can be
> different, so a separate SSL_CTX seems useful.
>
does this theoretically rule out usage
Peter Sylvester wrote:
It happened that I played with this a bit.
It is not just that you have a list of servers in one context, all
parameters of the server e;g. requirements for user certs etc can be
different, so a separate SSL_CTX seems useful.
does this theoretically rule out usage of 1
It happened that I played with this a bit.
It is not just that you have a list of servers in one context, all
parameters of the server e;g. requirements for user certs etc can be
different, so a separate SSL_CTX seems useful.
Enclosed a patch for the snapshot of today (try s_server and s_clien
Hi,
I am trying to write an http server which supports virtual servers & ssl
sessions. If I were to support the TLS 1.0 server name extension (which
says different virtual servers cud send different certificates), then
would I be able to use the same SSL_CTX across the different virtual
serve
