I haven't noticed the leak myself but I'm not running on high volume.
Upon closer inspection of libstirshaken it doesn't seem to care about freeing the certificate chain in many cases which could explain it regardless if any of the recent PRs are applied. Notably stir_shaken_cert_destroy() and stir_shaken_cert_deinit() seem to free the cert->x but not cert->xchain. https://github.com/signalwire/libstirshaken/blob/master/src/stir_shaken_ssl.c#L1822
I'll see if I can get another PR submitted to that project to deal with it.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.