very thanks for your response!
but i can not reproduce it. and i have not the output generated by
OPENSSL_asssert(). i will check my code. it is only occuer once in about 1.5
year.
在2009-03-11，"Ger Hobbelt" 写道：
>> my OpenSSL version is 0.9.8g. i find a crashed in OpenSSL. but it can
>>
Several comments:
1 - The Windows binary distribution of OpenSSL doesn't come
with libcrypto.a
2 - nm shows that RSA_new() is in libeay32.a
3 - libeay32.def shows RSA_new()
I believe that I have the libraries. I feel like I'm just
missing some makefile option, some Windows oddity, or some
gcc
> my OpenSSL version is 0.9.8g. i find a crashed in OpenSSL. but it can
> not reproduced. the backtraces list as blow:
[...]
> #0 0x005556ecc13c in raise () from /lib64/libc.so.6
> (gdb) bt
> #0 0x005556ecc13c in raise () from /lib64/libc.so.6
> #1 0x005556ecd998 in abort () fr
Forwarded to openssl-users for public discussion on how to debug
the problem.
Best regards,
Lutz
- Forwarded message from zlgodguy -
Date: Tue, 10 Mar 2009 17:22:21 +0800 (CST)
From: zlgodguy
To: r...@openssl.org
Subject: About OpenSSL crashed in 0.9.8g
hi all:
my OpenSS
Hi,
RSA_new is defined in libcrypto. It is obviously not defined in libeay32. You
can check it with "nm libeay32.a | grep RSA_new". Then you should probably get
a good copy of libcrypto.
BR,
Nikos
- Original Message -
From: Kenneth Goldman
To: openssl-users@openssl.org
Sent:
Hi,
I'm investigating upgrading the applications I'm responsible for from
SHA1 as the default PKCS#7 SignedData digest algorithm to stronger
digests such as SHA256, in ways that preserve backwards compatibility
for signature verifiers which do not support digest algorithms other
than SHA1. I want
What's the linker format when using [gcc / mingw] on Windows?
I am not using cygwin!
I assume I should use the libraries in .../OpenSSL/lib/MinGW,
but maybe not.
I've tried
-leay32
-L"C:/program files/openssl/lib/mingw/libeay32.a"
and even
copying libeay32.a to libcrypto.a and
Kyle Hamilton wrote:
On Mon, Mar 2, 2009 at 1:49 PM, Dr. Stephen Henson
wrote:
> ... The set of FIPS comparible ciphersuites is represented by the
> string "FIPS".
>
> In FIPS mode you cannot select any other ciphersuites: non FIPS
> ciphersuites are disabled.
Would it make any sense to allo
