Hi Willy, Christopher,

> Ideally we'd have the info in the ssl_ctx itself, but I remember that Emeric
> told me a while ago that we couldn't store anything in an ssl_ctx. Thus I
> can understand that we can't easily "tag" the ssl_ctx as being statically
> or dynamically allocated, which is why I understand the need for the flag
> on the connection as an alternative.

Well, I am not sure it will suit your needs, but it is possible to store
some info in a SSL_CTX using SSL_CTX_set_ex_data(). We are already doing
that for DH parameters and Certificate Transparency data.

-- 
Remi



Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to