no-cached-fetch option should do more
Open
Nobody has claimed this yet.
branch: master
triaged: feature
- Dominant language
- C
- Stars
- 30.8k
- Forks
- 11.5k
- Avg merge
- 10m
- Merged PRs (30d)
- 1
Description
The no-cached-fetch configure time option just turns off algorithm caching in libcrypto. It should go further and remove the caching code to save code size and run time memory use (caches are still allocated, for example).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the no-cached-fetch configure-time option through libcrypto and locating the algorithm cache allocation and implementation paths. Done means the option removes the caching code and cache allocations, reducing code size and runtime memory use while preserving the option's existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cryptography, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100