]> git.ipfire.org Git - thirdparty/strongswan.git/commit
projects / thirdparty / strongswan.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 3216646) | patch
leak-detective: Also ignore unknown memory freed in OPENSSL_cleanup() master
authorTobias Brunner <tobias@strongswan.org>
Fri, 5 Jun 2026 14:58:45 +0000 (16:58 +0200)
committerTobias Brunner <tobias@strongswan.org>
Fri, 5 Jun 2026 14:58:45 +0000 (16:58 +0200)
commit5fc403702b0109a907ef7e41f97c180e93c96e57
tree75c5222eb7131410939e75dab32ba922aac26faftree | snapshot
parent3216646bdbdecaa74f092564ba9c898311893042commit | diff
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.
src/libstrongswan/utils/leak_detective.c diff | blob | blame | history
Unnamed repository; edit this file 'description' to name the repository.