On 2/20/24 23:52, Ilya Maximets wrote:
> On 2/20/24 23:33, Alin Serdean wrote:
>> Thank you so much for the patches and dealing with this, Ilya!
>>
>> Regarding the MD / MT linking for a given binary, this can work, usually,
>> without any issues, although it will increase the memory used by the
On 2/20/24 23:33, Alin Serdean wrote:
> Thank you so much for the patches and dealing with this, Ilya!
>
> Regarding the MD / MT linking for a given binary, this can work, usually,
> without any issues, although it will increase the memory used by the process
> because both runtimes have to be
Thank you so much for the patches and dealing with this, Ilya!
Regarding the MD / MT linking for a given binary, this can work, usually,
without any issues, although it will increase the memory used by the process
because both runtimes have to be loaded.
We are linking the rest of the
On Tue, Feb 13, 2024 at 08:40:17PM +0100, Ilya Maximets wrote:
> OpenSSL 1.1.0 changed the library names from libeay32 and ssleay32 to
> standard libssl and libcrypto. All the versions of OpenSSL that used
> old names reached their official EoL, so it should be safe to just
> migrate to new
OpenSSL 1.1.0 changed the library names from libeay32 and ssleay32 to
standard libssl and libcrypto. All the versions of OpenSSL that used
old names reached their official EoL, so it should be safe to just
migrate to new names. They can still be supported via premium support
option, but I don't
