Closed huitema closed 1 year ago
The fix was to:
1) Move the "valgrind" test from a "no-fusion" branch to the "ci-test" branch 2) Force the ticket encryption to use "fusion", even if that consumes more mmory than using the OpenSSL variant of AES GCM.
Consider replacing that when the OpenSSL bug is fixed.
Running valgrind and using OpenSSL V3, we get reports such as:
This issue occurs when using the OpenSSL V3 implementation of AES GCM 128. The same test reported here uses the PTLS "fusion" implementation for the packet exchanges, and that one does not trigger any report. The reports here come from using the "openssl" implementation of encrypting and decrypting session tickets.
There is an OpenSSL bug for the same issue.