From: Tobias Brunner <tobias@strongswan.org>
Date: Fri, 5 Jun 2026 14:58:45 +0000 (+0200)
Subject: leak-detective: Also ignore unknown memory freed in OPENSSL_cleanup()
X-Git-Url: http://git.ipfire.org/gitweb/index.cgi?a=commitdiff_plain;h=HEAD;p=thirdparty%2Fstrongswan.git

leak-detective: Also ignore unknown memory freed in OPENSSL_cleanup()

It seems that 18a94525a7d5 was a bit hasty.  Apparently, it's still the
case that there were reports (at least in some test scenarios).  Luckily,
the new facility added in the previous commit allows us to whitelist
these allocations without having to ignore all unknown memory.
---

diff --git a/src/libstrongswan/utils/leak_detective.c b/src/libstrongswan/utils/leak_detective.c
index a3215014a2..616613a725 100644
--- a/src/libstrongswan/utils/leak_detective.c
+++ b/src/libstrongswan/utils/leak_detective.c
@@ -680,6 +680,7 @@ static char *whitelist[] = {
  */
 static char *unknown_memory_whitelist[] = {
 	"tzset",
+	"OPENSSL_cleanup",
 };
 
 /**