Hi ,
I have installed openssl from scratch and there I am not observing any
degradation. But I built it with in my project, there I observe the
degradation. The Configure file remains same , but still in my project I
can see a difference that "dynamic-engine" is present in enabled feature
list.
> From: vin
> To: openssl-users@openssl.org
> Date: 05/10/2019 12:44 AM
> Subject: Re: Issue in linking Openssl1.1.1b to application
> Sent by: "openssl-users"
>
> Hi Ken
>
> I am almost struck in registering the built dll to windows 7 32 bit
machine.
>
> Can you provide me the details on which a
Dear OpenSSL Users,
At my corporate environment, I'm experience a challenge to use openssl
s_client utility. I really appreciate if someone can help me narrow down
the issue.
Here the details -
Platform: RHEL 7.x
*Openssl version:*
OpenSSL 1.0.2k-fips 26 Jan 2017
built on: reproducible build, d
On 10/05/19 03:16, ramakrushna mishra wrote:
Hi ,
The results on a AIX machine looks more bad If I am interpreting them
correctly.
openssl 1.1.0e :
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes 64 bytes 256 bytes 1024 bytes 8192
bytes 16384 by
Hi,
On 10/05/19 02:29, ramakrushna mishra wrote:
Hi,
Could anyone please help me wth it.
Following are sslc speed results for SHA1.
[...]
OpenSSL 1.1.0e 16 Feb 2017
type 16 bytes 64 bytes 256 bytes 1024 bytes
8192 bytes 16384 bytes
sha1 90515.06k 301813
Hi,
I am trying to build the FIPS object module using the fips library
openssl-fips-2.0.16 on Ubuntu 18.04 for x86 arch.
I am following the steps in
https://wiki.openssl.org/index.php/FIPS_Library_and_Android
below steps are followed to Build the FIPS Object Module:
$ . ./setenv-android.sh
$ cd o
This seems to be caused by the ongoing saga documented in issues 6912 and 8102.
These functions were declared as weak in 1.1.1b.
safestack.h
# pragma weak OPENSSL_sk_num
# pragma weak OPENSSL_sk_value
# pragma weak OPENSSL_sk_new
# pragma weak OPENSSL_sk_new_null
...
lhash.h
# pragma weak O
Hi, all. Thanks for your help, I could finish compilation to the end.
However, athough I successfully compiled with _no-asm_ options, I found a
problem when loading the compiled library in the 3rd party code base.
When looking into the source code, the definition of some function seems to
require a
>> In a previous message, I saw:
> Does the Bind Type WEAK indicate anything?
Grasping at straws here, but I had to patch one of the assembler
files in the past on Solaris. The patch is below.
me% cd /path/to/openssl/src/crypto/bn/asm
me% patch < /tmp/sparcv9a-mont.pl.patch
Looks like
