leak-detective: Whitelist some Botan functions

Due to the mangled C++ function names it's tricky to be more specific.  The
"leaked" allocations are from a static hashtable containing EC groups.

There is another leak caused by the locking allocator singleton
(triggered by the first function that uses it, usually initialization of
 a cipher, but could be a hasher in other test runners), but we can avoid
that with a Botan config option.

diff --git a/src/libstrongswan/utils/leak_detective.c b/src/libstrongswan/utils/leak_detective.c
index b873e12a8cb243706896f5e1a42fbd93816d5cdc..08fcc0ef04f45d52c91d689c373ee08d85e45178 100644 (file)
--- a/src/libstrongswan/utils/leak_detective.c
+++ b/src/libstrongswan/utils/leak_detective.c
@@ -609,6 +609,11 @@ static char *whitelist[] = {
        /* FHH IMCs and IMVs */
        "TNC_IMC_NotifyConnectionChange",
        "TNC_IMV_NotifyConnectionChange",
+       /* Botan */
+       "botan_public_key_load",
+       "botan_privkey_create_ecdsa",
+       "botan_privkey_create_ecdh",
+       "botan_privkey_load_ecdh",
 };
 
 /**