Awesome, I sit corrected in this case. :)
In any case, though, it's generally best to plan to recompile. (Who says
that TLS 1.4 will be able to be implemented in a binary compatible
manner?) And even with this news, it is certainly a requirement that the
original poster must plan to replace the
> On Apr 3, 2017, at 8:42 PM, Kyle Hamilton wrote:
>
>
> In other words, it is very unlikely that TLS 1.3 can be implemented
> in a binary-compatible manner. It is best if you plan to recompile
> your application against the version of the library that implements
> TLS 1.3.
Unlikely or not, t
Every new version of TLS requires code to be written. Sometimes it can be
implemented in a binary compatible manner, and in those situations you can
get the implementation of a new TLS version by simply replacing a DLL or
equivalent dynamic library. However, it's much more likely that the
impleme
> On Apr 3, 2017, at 5:58 PM, Benjamin Kaduk via openssl-users
> wrote:
>
>> I have an query regarding TLS compatibility used in my application.
>> Currently we are using TLS1.2 to connect to a third party sever. Is there
>> any way to always use the highest TLS available version without modi
On 04/03/2017 04:42 AM, Hegde, Harsha wrote:
>
> Hi,
>
> I have an query regarding TLS compatibility used in my application.
> Currently we are using TLS1.2 to connect to a third party sever. Is
> there any way to always use the highest TLS available version without
> modifying or recompiling the a
Hi,
I have an query regarding TLS compatibility used in my application. Currently
we are using TLS1.2 to connect to a third party sever. Is there any way to
always use the highest TLS available version without modifying or recompiling
the application code whenever there is any new version of TLS
