> The way I normally trace this stuff is to run it under a debugger first to
> get the addresses of leaks then a second time with conditional breakpoints
> added at those points so that when that same address is allocated it is
> possible to do a stack trace to see the precise cause.
>
> That ex_da
Ok, thanks a lot. The "patch" utility was the missing piece.
Pierre De Boeck
Sr System Engineer
Cipherquest
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Afchine
> Madjlessi
> Sent: Friday, July 04, 2003 6:10 PM
> To: [EMAIL PROTECTED]
> Subje
From: "Pierre De Boeck" <[EMAIL PROTECTED]>
> Hi all,
>
> I just downloaded the 0.9.7b version of OpenSsl and I expected
> to see PKCS11 support in the form of an ENGINE instance.
>
> But apparently that particular engine is not yet bundled with
> the rest and so I downloaded the "hw_pkcs11-0.9.7
Hi all,
I just downloaded the 0.9.7b version of OpenSsl and I expected
to see PKCS11 support in the form of an ENGINE instance.
But apparently that particular engine is not yet bundled with
the rest and so I downloaded the "hw_pkcs11-0.9.7b" patch (
in the contribution link) which should
In message <[EMAIL PROTECTED]> on Fri, 04 Jul 2003 18:34:42 +0530,Fri, 4 Jul 2003
19:01:21 +0530, "arun" <[EMAIL PROTECTED]> said:
arunks> I am using "OpenSSL 0.9.6b [engine] 9 Jul 2001" on Red Had
arunks> Linux. I have compiled it with my application. Things were
arunks> fine until I added singa
Hello,
I am using "OpenSSL 0.9.6b [engine] 9 Jul 2001" on Red Had Linux. I have
compiled it with my application. Things were fine until I added singal
handling code for my application. I blocked all signals at application
startup and have handling code for SIGINT alone. After the addition of
signa
hi again,
here is a dummy example that reads the key usage extension from a
certificate.
thanks Steve.
regards,
aleix
==
int
main(int argc, char** argv)
{
FILE* in;
int pos;
int crit;
X509* cert;
X509_EXTENSION* ext;
ASN1_B
For supporting OpenSSL in the embedded web server, I am
trying to find out which encryption algorithms are the best to support: I would
decide based on which algorithms are most commonly supported, rated best in
terms of security and also on the performance. Is there any comparison
availabl
On Thu, Jul 03, 2003 at 10:47:27PM -0400, Thomas J. Hruska wrote:
> For non-blocking BIOs (in this case, non-blocking sockets), the
> documentation is unclear as to whether or not a second call to
> SSL_shutdown() will block:
>
> "The second call will make SSL_shutdown() wait for the peer's "close
