seg-fault in malloc called from DH_compute_key

Hi, I am observing a seg-fault with following back-trace- #0 0x089277fe in _int_malloc () #1 0x08926a72 in malloc () #2 0x087df811 in default_malloc_ex (num=4, file=0x89eda40 bn_lib.c, line=336) at mem.c:79 #3 0x087dfe30 in CRYPTO_malloc (num=4, file=0x89eda40 bn_lib.c, line=336) at

Re: seg-fault in malloc called from DH_compute_key

General hint: seg-faults in malloc(), free(), realloc() etc. are usually caused by earlier corruption of the heap. Looking at the stack at the time of crash is rarely successful. A better hint is to link to a special debug variant of malloc(), which is specifically designed to report the exact

Fully Hashed MQV (FHMQV) (Key Agreement)

Hi All, Is anyone interested in implementing FHMQV in OpenSSL? I recently implemented FHMQV in Crypto++ (hopefully the patch will be submitted soon). But I don't have a reference implementation to test it against (or interoperate with). If interested, I can provide a Crypto++ reference for

pkcs7 verification with ruby

I have a pkcs7 message that contains a chain of certificates. The root certificate is the Apple CA. I am using ruby to verify the message and I have something that I think works, but I am wondering if there is a much easier method of doing what I am doing My specific question is in regards