ilan
> -Original Message-
> From: Jesse Pelton [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 25, 2005 4:11 PM
> To: security-dev@xml.apache.org
> Subject: RE: XML-Security-C memory leak
>
>
> It has been a couple of weeks, and this change doesn't seem
>
> From: Berin Lautenbach [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, March 08, 2005 5:43 AM
> To: security-dev@xml.apache.org
> Subject: Re: XML-Security-C memory leak
>
> Jesse Pelton wrote:
> > OpenSSLCryptoBase64::b642BN() leaks memory in the following line:
> >
&
ere's any harm in calling them:
RAND_cleanup()
X509_TRUST_cleanup()
ERR_remove_state(0)
-Original Message-
From: Berin Lautenbach [mailto:[EMAIL PROTECTED]
Sent: Tue 3/8/2005 5:42 AM
To: security-dev@xml.apache.org
Subject: Re: XML-Security-C memory leak
Jesse Pe
Hello All
I wonder if I have been boycotted from the xml security mailing list, coz no
one has addressed my plea for help with XML DSig.
Anyways, I have been able to generate and validate an enveloped signature.
Another problem beckons me now, if someone could please help me out with it.
It so
Jesse Pelton wrote:
OpenSSLCryptoBase64::b642BN() leaks memory in the following line:
return BN_dup(BN_bin2bn(buf, bufLen, NULL));
BN_bin2bn() allocates a BIGNUM, so there's no need to dup it, and doing
so causes the first one to leak.
Thanks! Will fix in CVS on the weekend.
Cheers,
OpenSSLCryptoBase64::b642BN() leaks memory in the following line:
return BN_dup(BN_bin2bn(buf, bufLen, NULL));
BN_bin2bn() allocates a BIGNUM, so there's no need to dup it, and doing
so causes the first one to leak.
This is not the only leak I'm seeing in my app, but it's the only one
I'
