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 a3215014a2cfbf740a8eeacf77b14a06e4e3c5ae..616613a7250cde8e90f03b44ed08254acdaecf1b 100644 (file)
--- 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",
 };
 
 /**