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 Babin-Ebell <[EMAIL PROTECTED]> wrote:
Goetz Babin-Ebell <[EMAIL PROTECTED]> wrote:
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 a closer look at the code it looks like
> these buffers just act as a scratch buffers. With this change I could
> reduce the memory usage per SSL session significantly.
>
> I just want to make sure that this does not cause any other problem. Any
> advice from OpenSSL Guru's is really appreciated.
I am not a OpenSSL Guru but I think you should
test a Renogiation after You freed the buffers and see what happens...
Bye
Goetz
--
DMCA: The greed of the few outweighs th e freedom of the many
Yahoo! Mail Mobile
Take Yahoo! Mail with you! Check email on your mobile phone.
