Re: [openssl-users] Handle Leaks - shmem-win32.c shmem.c - OpenSSL 1.0.1l

2015-01-24 Thread Michel SALES
Hi, Just a quick answer : I didn't find any call to CloseHandle() function in your code. Best regards, Michel. ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

Re: [openssl-users] Handle Leaks - shmem-win32.c shmem.c - OpenSSL 1.0.1l

2015-01-25 Thread Michel SALES
(); sk_SSL_COMP_free( SSL_COMP_get_compression_methods()); _CrtDumpMemoryLeaks(); return 0; } Hope it helps, Michel De : openssl-users [mailto:openssl-users-boun...@openssl.org] De la part de Avery A. Tarasov Envoyé : samedi 24 janvier 2015 22:34 À : openssl-users@openssl.org Objet : Re

Re: [openssl-users] Handle Leaks - shmem-win32.c shmem.c - OpenSSL 1.0.1l

2015-01-25 Thread Michel SALES
in this case. I am not sure to fully understand what your are doing now, but with the modified version I've sent to you, _CrtDumpMemoryLeaks() doesn't report any problem on my Windows 7 64 bits machine. Just another quick idea : why not try _beginthread() instead of CreateThread() ? Michel

BorlandC++ 6 compiler Options

2005-08-12 Thread Jean-Michel Lekston
I keep this error. Is there here to help me please? Jean-Michel Lekston Cogendi Phone: +33 (1) 41 91 75 75

PHP failure compile with --openssl : e_os.h don't exist in OpenSSL-0.9.7b under Solaris 2.7

2002-07-12 Thread Michel Mac Wing
: ld returned 1 exit status *** Error code 1 make: Fatal error: Command failed for target `libphp4.la' Current working directory /udd/mmacwing/usr/src/php-4.2.1 *** Error code 1 make: Fatal error: Command failed for target `all-recursive' Thanks for your help. Michel

WG: OCSP response signature verification

2010-03-12 Thread Michel Pittelkow - michael-wessel . de
- Response verify OK S999D003:/tmp/ocsp # Kind regards, Michel Pittelkow

RE: WG: OCSP response signature verification

2010-03-12 Thread Michel Pittelkow - michael-wessel . de
Sure! Here are the request and response files. Kind regards Michel Pittelkow Hi everyone, we are currently trying to verify an ocsp response. The return is Response verify OK but we need to verify the signature algorithm of the response signature. We tried putting the response

AW: WG: OCSP response signature verification

2010-03-12 Thread Michel Pittelkow - michael-wessel . de
I forgot to write, which versions are used. For the client we are using 0.9.8L. But we also tested with M. We are not sure about the responders but we are trying to find out. Kind regards Michel Pittelkow Hi everyone, we are currently trying to verify an ocsp response. The return

AW: WG: OCSP response signature verification

2010-03-12 Thread Michel Pittelkow - michael-wessel . de
of data. Sorry. I am not that into C though :-( Kind regards Michel Pittelkow I forgot to write, which versions are used. For the client we are using 0.9.8L. But we also tested with M. We are not sure about the responders but we are trying to find out. Oops, there was a bug in the print

AW: WG: OCSP response signature verification

2010-03-12 Thread Michel Pittelkow - michael-wessel . de
:df:d2:4b:f4:e1:dd:9e:31:48:21:95:08:0e:67:6f: 49:e1:ab:77:11:cf:61:dc:ae:d3:38:a3:fb:54:36:70:bc:1a: 56:47:22:fe Certificate: Data: Kind regards Michel Pittelkow Ah! That's exactly the point, where I tried to edit the code and recompile it. But every time I tried to I became

<    1   2