On 16/11/16 23:22, Dan S wrote:
> I thought there is anything that would stop you from compiling with
> everything and make choices at run time, (TLSv1_2_method,
> TLSv1_1_method, TLSv1_method, SSLv23_method etc... just set the right
> flags and cyphers)
Do not use the TLS*method() functions for
I thought there is anything that would stop you from compiling with
everything and make choices at run time, (TLSv1_2_method, TLSv1_1_method,
TLSv1_method, SSLv23_method etc... just set the right flags and cyphers)
On Wed, Nov 16, 2016 at 2:58 PM, craig_we...@trendmicro.com <
craig_we...@trendmicr
On 16/11/16 22:58, craig_we...@trendmicro.com wrote:
> I am an OpenSSL neophyte, so please bear with me if the answer is
> obvious in the documentation.
>
>
>
> Our product is going to provide runtime options to the user to enable
> and disable TLS 1.0, 1.1 and 1.2 in a discrete manner. For e
On Wed, Nov 16, 2016 at 10:58:17PM +, craig_we...@trendmicro.com wrote:
> Our product is going to provide runtime options to the user to enable and
> disable TLS 1.0, 1.1 and 1.2 in a discrete manner.
This is a bad interface. Do not implement this feature. Instead
support only a contiguous
