just curious if you see a memleak with that code and libstirshaken with PR124.

I applied the patch to branch 5.6 and can see the free memory going down since the last restart.

It seems to be caused by the call to stirshaken_check_identity(), as commenting it and using secsipid_check_identity("") no leaks are present ( did an A/B test with same config just a line commented out ).

Params tested and still leaking:

cache certificate on or off.
root chain validation on or off.
vs_*_pvname set or unset.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.