summaryrefslogtreecommitdiffstats
path: root/.github/workflows/cross-compiles.yml
diff options
context:
space:
mode:
authorMatt Caswell <matt@openssl.org>2024-03-13 15:19:43 +0000
committerMatt Caswell <matt@openssl.org>2024-03-15 18:10:49 +0000
commitdc9bc6c8e1bd329ead703417a2235ab3e97557ec (patch)
tree260bfd5f378d5497cf35fd4eeed9e9e3f26adda6 /.github/workflows/cross-compiles.yml
parentbc3eb7b52789bdea457e4fdff6e25da340c88901 (diff)
Fix unbounded memory growth when using no-cached-fetch
When OpenSSL has been compiled with no-cached-fetch we do not cache algorithms fetched from a provider. When we export an EVP_PKEY to a provider we cache the details of that export in the operation cache for that EVP_PKEY. Amoung the details we cache is the EVP_KEYMGMT that we used for the export. When we come to reuse the key in the same provider that we have previously exported the key to, we check the operation cache for the cached key data. However because the EVP_KEYMGMT instance was not cached then instance will be different every time and we were not recognising that we had already exported the key to the provider. This causes us to re-export the key to the same provider everytime the key is used. Since this consumes memory we end up with unbounded memory growth. The fix is to be more intelligent about recognising that we have already exported key data to a given provider even if the EVP_KEYMGMT instance is different. Reviewed-by: Tomas Mraz <tomas@openssl.org> Reviewed-by: Neil Horman <nhorman@openssl.org> Reviewed-by: Paul Dale <ppzgs1@gmail.com> (Merged from https://github.com/openssl/openssl/pull/23841)
Diffstat (limited to '.github/workflows/cross-compiles.yml')
0 files changed, 0 insertions, 0 deletions