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 Mon, Apr 3, 2017 at 5:49 PM, Benjamin Kaduk wrote:
> On 04/02/2017 07:42 PM, Jeffrey Walton wrote:
>
> I was looking at Kurt Roeckx 's patches for OpenSSH at
> https://github.com/openssh/openssh-portable/pull/48/files. See
> libcrypto-compat.h and libcrypto-compat.c.
>
> Are the source files di
> 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
On 04/02/2017 07:42 PM, Jeffrey Walton wrote:
> I was looking at Kurt Roeckx 's patches for OpenSSH at
> https://github.com/openssh/openssh-portable/pull/48/files. See
> libcrypto-compat.h and libcrypto-compat.c.
>
> Are the source files distributed by OpenSSL? If so, where is the download?
>
> If
> On Apr 3, 2017, at 4:26 PM, Benjamin Kaduk wrote:
>
> There was a fair amount of churn in x509_vfy.c with the inclusion
> of the DANE stuff and whatnot, so it's not immediately clear to me
> when this change actually happened. I think there are good
> arguments for the current 1.1.0 behavior
Still - I couldn't find the root-cause why OpenSSL is closing after
responding. Any pointers about which area of codebase is causing this
will be very helpful. Is there any commercial support available for
OpenSSL?
On Wed, Mar 29, 2017 at 6:47 AM, Kaja Mohideen wrote:
> It responds and then close
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
10 matches
Mail list logo
