Hi All,
I am seeing an issue with the routine CRYPTO_cbc128_encrypt() in version
1.0.2h where,
, if I have not declared STRICT_ALIGNMENT, application crashes
intermittently.
There was a similar query here but for CRYPTO_ctr128_encrypt.
https://mta.openssl.org/pipermail/openssl-dev/2016-January/00
On Wed, 13 Mar 2019 17:56:16 +0100,
Salz, Rich via openssl-users wrote:
> It would be really good if code being merged to master had --strict-warnings
> and the mdebug
> backtrace stuff turned on. In the past few days there have been a flurry of
> checkins that these
> flags would have caught.
W
It would be really good if code being merged to master had --strict-warnings
and the mdebug backtrace stuff turned on. In the past few days there have been
a flurry of checkins that these flags would have caught.
Well, flurry is admittedly too strong. …
You might want to show the whole command line that caused this error,
and it would help if we could have a look at the libcrypto.map you
got.
To be more effective, it might be a good idea to create an issue for
this on github: https://github.com/openssl/openssl/issues/new/choose
Cheers,
Richard
Hello everyone,
I am working on a project about how to use openssl libs to implement a
PAdES(whitch is based on CAdES) signature because I saw that the master branch
of openssl has supported CAdES-BES signature. But now there is a problem I
don't know how to solve it. So I am asking for som
Hi,
Trying to build openssl-1.1.1b on solaris sparc 32 bit machine.
Getting some error with respect to "file format not recognized"
-lsocket -lnsl -ldl -pthread
/v/toolchain/SunOS-5.10-sparc/binutils-2.30/bin/gld:libcrypto.map: file
format not recognized; treating as linker script
/v/
