LibreSSL: free memory allocated by tls_init()

Question

When using LibreSSL's libtls, is it possible to free the memory that is allocated by tls_init()?

I found using valgrind that a simple program that only calls tls_init() code leaves 2058 blocks of memory "still reachable". I am aware that "still reachable" memory is not strictly a memory leak and it will be cleaned up by the OS when the program exits... But it makes identifying my own memory issues much more obnoxious.

OpenSSL's SSL_library_init() doesn't seem to have the same problem.

I'm on Linux with a source build from the libressl-portable github page.

rexroni · Accepted Answer · 2018-05-03T03:21:51.160

1

This question was also asked on the libressl mailing list. The answer is no, at least not with the current libtls API.

The current best alternative for memory testing with valgrind is to use the --suppressions option.

edited May 03 '18 at 03:21

answered May 02 '18 at 22:13

rexroni

433
4
13

Nice finding! For future reference it may be useful to also add a link to the relevant mail in the mailing list (if it's public). – Matteo Italia May 02 '18 at 22:17
Never mind, I found them and added them to the answer. – Matteo Italia May 02 '18 at 22:30

LibreSSL: free memory allocated by tls_init()

1 Answers1