Hi,
I obtain the following error leak summary with Valgrind for a single SSL
connect with the server
==20626== 3,689 (200 direct, 3,489 indirect) bytes in 1 blocks are
definitely lost in loss record 134 of 147
==20626==at 0x40046C1: malloc (vg_replace_malloc.c:149)
==20626==by 0x4565E6A:
Hello!
Am 14.04.2007 um 00:04 schrieb Dr. Stephen Henson:
'tis done.
I found a quiet period to look into it and test it a little. Check
out the new
-stream option in the smime utility for OpenSSL 0.9.9.
Support in the API is quite simple too, just include the
PKCS7_STREAM flag in
the
oh, I forgot to mention that this behaviour appears in the latest
snapshot (20070816) of openssl-0.9.9-dev.
Am 16.08.2007 um 10:30 schrieb Harald Latzko:
Hello!
Am 14.04.2007 um 00:04 schrieb Dr. Stephen Henson:
'tis done.
I found a quiet period to look into it and test it a little
Hi,
I'm trying to write a pkcs7 object with following code to a file:
unsigned char *tmp, signature;
int iLen;
iLen = i2d_PKCS7(p7, NULL);
signature = (unsigned char*) malloc(iLen);
tmp = signature;
iLen = i2d_PKCS7(p7, tmp);
FILE *fpkcs7 = fopen(C:\\sig.p7s, w+);
for(int i =
On Thu, Aug 16, 2007 at 03:58:19PM +0200, Christian Wiesbauer wrote:
Hi,
I'm trying to write a pkcs7 object with following code to a file:
unsigned char *tmp, signature;
unsigned char *tmp, *signature;
int iLen;
iLen = i2d_PKCS7(p7, NULL);
signature = (unsigned
Thanks for the response.
You'll have to bear with me, as I'm not really a low-level sockets
programmer. But maybe you misunderstood the nature of my problem.
The problem is that, on Windows at least, my server doesn't appear to
get the SSL shutdown notify packet, for some reason. So, if that
Prabhu S wrote:
Is this a memory leak. If I run the client application under stress, I
run into issues with available swap size reducing to zero( free -m
command) ..I have resolved significant application memory leak. Still I
run into problem in stress test.
Any suggestions?
There is a
Shaw Graham George wrote:
The problem is that, on Windows at least, my server doesn't appear to
get the SSL shutdown notify packet, for some reason. So, if that is
to be expected, I'm looking for an alternative way of detecting the
closure.
I've now tested it on Linux, and the existing code
Sure.
1. The server receives the HTTP request, using SSL_read() and
SSL_pending(). The request contains a Keep-Alive request.
2. The server writes the data out to another process.
3. The server then it sits on an event handler that multiplexes a
select() (or Windows equivalent) on sockets it
dear list,
i'm having a real adventure trying to get gsoap openssl to behave
consistently and i would appreciate some pointers before i run out of
hair completely.
i'm on MacOS X 10.4.9 but i shifted over to Linux Fedora Core 2
because debugging on the Mac is impossible thanks to the
Shaw Graham George wrote:
Sure.
1. The server receives the HTTP request, using SSL_read() and
SSL_pending(). The request contains a Keep-Alive request.
2. The server writes the data out to another process.
3. The server then it sits on an event handler that multiplexes a
select() (or
Side track: Is it possible to make the window platform listen on 31
sockets at once per thread ? (or whatever is small limit was)
IOCP.
Okay you closed your ears to the read event ? On Unix the select() has
an exceptfds which can be used to pickup a socket error/close (but may
not be
dear list,
further to my question earlier today i've been able to figure out
what's going on and i have an interim solution, though i think the
situation warrants an openssl bug report.
in my micro-app, i wasn't setting up any client or server
verification requirements. these seem to
Hello,
I have tried sending the following email to openssl-users@openssl.org
after subscribing to the list but somehow my emails dont seem to be
reaching anyone. I was wondering if you could help with the questions
below, or send it to the list on my behalf and CC me. I really
appreciate
Hi Christian,
thanks a lot for your response!
FILE *fpkcs7 = fopen(C:\\sig.p7s, wb+);
solved my problem!
Thanks a lot!!!
Christian
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag von Christian Hohnstaedt
Gesendet: Donnerstag, 16. August 2007
15 matches
Mail list logo