-Original Message-
From: openssl-users On Behalf Of Michael
Wojcik
Sent: Thursday, January 21, 2021 9:28 AM
To: openssl-users@openssl.org
Subject: RE: OpenSSL 1.1.1g Windows build slow rsa tests
> >From: openssl-users On Behalf Of
> >Dr Paul Dale
> >Sent: Wednesday, 20 January, 2021
Hello,
I'm building openssl 1.1.1g on multiple platforms and I found that the rsa
speed tests are significantly slower in my build than on the other OS platforms
(Linux and macOS).
I downloaded a Windows 64-bit binary distribution of openssl from
Hello,
I updated from 1.1.1d to the latest version 1.1.1g and had a build error on
macOS 10.8 for the 64-bit crypto library. I rolled back to 1.1.1e and
reproduced the build error.
32-bit is building fine, only 64-bit has the issue. I looked at the commits
for 1.1.1e and nothing jumped out
Thank you for the information, Victor.
>> I upgraded a library that used OpenSSL 1.0.2 to the OpenSSL 1.1.1d.
>> On Windows, I have found that the time to decrypt had doubled. After
>> a bit of timestamp logging, I found the RSA_private_decrypt function
>> is taking twice as long with 1.1.1d
I upgraded a library that used OpenSSL 1.0.2 to the OpenSSL 1.1.1d. On
Windows, I have found that the time to decrypt had doubled.
After a bit of timestamp logging, I found the RSA_private_decrypt function is
taking twice as long with 1.1.1d as it did with 1.0.2t. This is being called
from a
> > > >The no-dso is silently not valid in 1.1.1c. That option didn't work
> > > >right, so it was unusable in practice anyway. However, someone recently
> > > >fixed that up, unfortunately after the last 1.1.1 release.
> > > >The specific patch may be possible to find on github (unless that
>The no-dso is silently not valid in 1.1.1c. That option didn't work right, so
>it was unusable in practice anyway. However, someone recently fixed that up,
>unfortunately after the last 1.1.1 release.
>The specific patch may be possible to find on github (unless that branch has
>been
Please bear with me as I am a Windows developer, and not too adept with Linux.
Our library has been using the OpenSSL 1.0.2x branch, and we are moving to
1.1.1c. I have the Windows build of our libraries working, and now I've moved
to Linux.
Our library is built as a shared library as well as
>The output certainly suggests something is calling TlsAlloc between the call
>made for destructor_key.value and the one for private_drbg, and that index is
>never freed. You always get 7 when allocating destructor_key.value because
>that >index was freed when you unloaded OpenSSL, and so it's
On 09/08/2019 14:33, Dan Heinz wrote:
>> I have a static library using OpenSSL (built as static library with
>> the no-pinshared parameter in the configuration) that is then included
>> in a DLL that gets loaded and unloaded many times by the calling
>> applica
I have a static library using OpenSSL (built as static library with the
no-pinshared parameter in the configuration) that is then included in a DLL
that gets loaded and unloaded many times by the calling application. Now that
the code is in 1.1.1c to allow me to manually shutdown the OpenSSL
Is there currently a way to manually shutdown the OpenSSL library?
We have a DLL that statically links OpenSSL. Our DLL gets loaded and unloaded
multiple times by a process (not our process), and we need to release OpenSSL
each time. This was not possible with OpenSSL 1.1 as of September
We have not moved from OpenSSL 1.0.x to OpenSSL 1.1.x as we require the ability
to manually shutdown the library. We noticed in the latest release notes the
following:
"Modify compression code so it frees up structures without using the ex_data
callbacks. This works around a problem where some
The original issue was discussed here:
https://www.mail-archive.com/openssl-users@openssl.org/msg80781.html
To summarize: We have a DLL that statically links OpenSSL. Our DLL gets loaded
and unloaded multiple times by a process (not our process), and we need to
release OpenSSL each time.
>>>> On 04/01/17 23:11, Dan Heinz wrote: Using openssl 1.1.0c.
>>>>
>>>> I have a test application that is a win32 console app that calls a >
>>> win32 DLL which has the openssl libraries linked in statically>.
>>>>
&g
>>On 04/01/17 23:11, Dan Heinz wrote:
>> Using openssl 1.1.0c.
>>
>> I have a test application that is a win32 console app that calls a
>> win32 DLL which has the openssl libraries linked in statically.
>>
>> The test applications uses late-bi
Using openssl 1.1.0c.
I have a test application that is a win32 console app that calls a win32 DLL
which has the openssl libraries linked in statically.
The test applications uses late-binding to the DLL and calls LoadLibrary for
the DLL, one test function in the DLL, and then FreeLibrary on the
17 matches
Mail list logo
