Hi,
I tried to install openssl with my system x86-64 and use intel c compiler
instead of gcc, i.e. Configure linux-x86_64-icc. It turns out that it can't
pass the command make test. The testlog is attached.
I wonder whether it is because openssl doesn't support the configuration for
x86-64
On Wed, 04 Mar 2009 21:40:52 +, Tanguy Fautré said:
We've figured the try/except modification was safe for the following
reasons.
- The traversal is read-only. Trapping an access violation/segfault in
this case is safe (i.e. we do not modify an unknown memory location).
- The
I think you want a key, not the group.
EC_GROUP_new_by_curve_name = EC_KEY_new_by_curve_name
Billy
On Mon, Mar 2, 2009 at 6:15 PM, neorom neo...@gmail.com wrote:
I resolved my previous problem, the error came in the name of the
variable key which has to be named eckey. So there is a mistake
I work on a commercial product that uses OpenSSL internally (0.9.8j).
Recently, we received a crash dump from a customer in the field (our
first I think), and we believe we tracked it down to a leak on our
part.
Nevertheless, it would be nice if memory exhaustion didn't lead to
dereferencing a
Hi Bhanu,
There are precompiled binary versions of OpenSSL (0.9.7m/0.9.8h) available for
HP-UX that may not have this problem:
http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=OPENSSL11I
After installing the depot the /opt/openssl/src directory contains the source
--- crypto\pkcs12\p12_crt.c � Wed Mar �4 13:37:26 2009
+++ crypto\pkcs12\p12_crt.c � �Wed Mar �4 12:44:40 2009
@@ -168,7 +168,8 @@ PKCS12 *PKCS12_create(char *pass, char *
�� � � �sk_PKCS12_SAFEBAG_pop_free(bags, PKCS12_SAFEBAG_free);
�� � � �bags = NULL;
- � � � p12 = PKCS12_add_safes(safes,
Oh, one more thing. This is a very common type of error. It's very hard
to test all possible out-of-memory paths. Worse, leaks in the error paths is
common (your submitted fix even had one) making it hard to recover from an
out-of-memory condition.
If you are trying to code
On Thu, Mar 5, 2009 at 6:41 PM, David Schwartz dav...@webmaster.com wrote:
--- crypto\pkcs12\p12_crt.c Wed Mar 4 13:37:26 2009
+++ crypto\pkcs12\p12_crt.c Wed Mar 4 12:44:40 2009
@@ -168,7 +168,8 @@ PKCS12 *PKCS12_create(char *pass, char *
sk_PKCS12_SAFEBAG_pop_free(bags,
What if the best solution is to abort the operation requesting the big
chunk of unavailable memory? We don't have any significant cache in
this process to dump, and it wouldn't have helped for long anyway.
That should be handled in the code that deals with requesting big chunks of
memory.