This is openssl-1.0.1k on Fedora 21 x86_64, but it should not matter, here
is a brief analysis:
Consider sv_body() in server.c
2237 con=SSL_new(ctx);
Here a new context is initialized. From ssl_lib.c:295, this also causes the
krb context to be initialized via
295 s->kss
This is openssl-1.0.1k on Fedora 21 x86_64, but it should not matter, here
is a brief analysis:
Consider sv_body() in server.c
2237 con=SSL_new(ctx);
Here a new context is initialized. From ssl_lib.c:295, this also causes the
krb context to be initialized via
295 s->kss
On Thu Jan 15 14:25:54 2015, sidhpurwala.huza...@gmail.com wrote:
> Here is how to test it:
>
> openssl req -x509 -newkey rsa -keyout localhost.key -out localhost.crt
> -subj \
> /CN=localhost -nodes -batch -sha256
>
> valgrind --leak-check=full openssl s_server -key localhost.key -cert \
> localho
Here is how to test it:
openssl req -x509 -newkey rsa -keyout localhost.key -out localhost.crt -subj \
/CN=localhost -nodes -batch -sha256
valgrind --leak-check=full openssl s_server -key localhost.key -cert \
localhost.crt -accept 4433
./poc.py
Every run of poc.py causes 56 byte memory leak:
Here is how to test it:
openssl req -x509 -newkey rsa -keyout localhost.key -out localhost.crt -subj \
/CN=localhost -nodes -batch -sha256
valgrind --leak-check=full openssl s_server -key localhost.key -cert \
localhost.crt -accept 4433
./poc.py
Every run of poc.py causes 56 byte memory leak:
On Thu Jan 15 10:38:58 2015, sidhpurwala.huza...@gmail.com wrote:
> Hi,
>
> I found a memory leak in s_server.c. On my x86_64 machine, this leaks 56
> bytes for each connection request.
>
> Patch is attached.
I'm not seeing this memory leak. The kctx object should be being freed in the
call to SSL
Hi,
I found a memory leak in s_server.c. On my x86_64 machine, this leaks 56
bytes for each connection request.
Patch is attached.
patch
Description: Binary data
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/op
