gcrypt: Explicitly initialize RNG backend to allocate static data

The libgcrypt RNG implementation uses static buffer allocation which it does
not free. There is no symbol we can catch in leak-detective, hence we explicitly
initialize the RNG during the whitelisted gcrypt_plugin_create() function.

diff --git a/src/libstrongswan/plugins/gcrypt/gcrypt_plugin.c b/src/libstrongswan/plugins/gcrypt/gcrypt_plugin.c
index 480c083c05d195d7e8133b3d3fdc5154544ff54e..04f1f43ef17380a1163e38a1525bd159e9a42037 100644 (file)
--- a/src/libstrongswan/plugins/gcrypt/gcrypt_plugin.c
+++ b/src/libstrongswan/plugins/gcrypt/gcrypt_plugin.c
@@ -158,6 +158,9 @@ plugin_t *gcrypt_plugin_create()
        }
        gcry_control(GCRYCTL_INITIALIZATION_FINISHED, 0);
 
+       /* initialize static allocations we want to exclude from leak-detective */
+       gcry_create_nonce(NULL, 0);
+
        INIT(this,
                .public = {
                        .plugin = {