Title: Re: SSL per session memory usage
Prashant Kumar wrote:
Hello Goetz,
Thank you for your input. I tested re-negotiation and it works fine with this change \
since while doing re-negotiate the OpenSsl returns SSL_ERROR_WANT_READ or \
SSL_ERROR_WANT_WRITE in which case I
Roger,
What I have found is that OpenSsl allocates s3-rbuf and s3-wbuf as soon as the SSL session is created, however uses these buffers as scratch buffer while doing handshake, or doing any other SSL opertion. Once the operation is done, those buffers could be safely freed since then do not hold
Prashant Kumar wrote:
Hello Group,
Hello Prashant,
The workaround of freeing s3-rbuf and s3-wbuf after the handshake is
complete and after SSL_read, SSL_write, SSL_shutdown and so on returns
success really seems to work. I have tested it running openssl as a SSL
client and as a server. Taking
Hello Goetz,
Thank you for your input. I tested re-negotiation and it works fine with this change since while doing re-negotiate the OpenSsl returns SSL_ERROR_WANT_READ or SSL_ERROR_WANT_WRITE in which case I will not free the buffer until the handshake is done.
Regards,
Prashant.Goetz
Hello Group,
The workaround of freeing s3-rbuf and s3-wbuf after the handshake is complete and after SSL_read, SSL_write, SSL_shutdownand so on returns success really seems to work. I have tested it running openssl as a SSL client and as aserver. Taking a closer look at the code it looks like
Hello All,
I was doing some scaling testing to find out how much memory does OpenSsl use per TLS session. I see that OpenSsl pre-allocates around 34821 bytes for "rbuf" and 18698 bytes for "wbuf" in "ssl3_setup_buffers" to match with the packet size defined in the RFC. Did anyone try modifying
!
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Prashant Kumar
Sent: Tuesday, May 03, 2005 8:40 AM
To: openssl-dev@openssl.org
Subject: SSL per session memory usage
Hello All,
I was doing some scaling testing to find out how much memory does OpenSsl
use
Hello Steve,
Thank you for your help. I will look at section 3.2 of the RFC. As a workaround for this memory usage limitatioin, I free the "s3-rbuf" and "s3-wbuf" once the handshake is done. I allocate "s3-rbuf" and "s3-wbuf" during SSL_read, SSL_write, SSL_shutdown and so on. Once these calls
