openssl/openssl

Application context to set in CRYPTO_set_mem_functions

Open

#22,329 opened on Oct 10, 2023

View on GitHub
 (7 comments) (0 reactions) (0 assignees)C (11,262 forks)batch import
backlog fixbranch: masterhelp wantedtriaged: feature

Repository metrics

Stars
 (30,157 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Hello Team,

After reviewing the documentation for CRYPTO_set_mem_functions,

I've noticed that the current implementation restricts us to set application memory callbacks for per objects. Unfortunately, this limitation doesn't align well with my use case.

In my scenario, I'm dealing with multiple objects, each of which has its own memory allocation, reallocation, and deallocation functions. Since the current callback mechanism lacks an application context, and I couldn't find any other suitable OpenSSL API to access specific application contexts, I'm unable to utilize memory callbacks to invoke the memory functions of individual objects.

I kindly request that you consider accepting this feature request. It would greatly enhance the flexibility and usefulness of the OpenSSL library. I'm eager to know if this feature could be made available in OpenSSL 3.0.10 or a future release.

Thank you for your attention to this matter.

Contributor guide

Research direction
Study the existing CRYPTO set mem functions API and its usage. Propose a new API that accepts an application context parameter. Ensure backward compatibility by keeping the old function as a wrapper. Implement changes in the memory allocation functions to pass the context. Update all internal callers to use the new API. Write tests for the new functionality.
Tech stack
c
Domain
securityapi
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
COpenSSL internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20