New API to get extension by OID is needed.
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 30.8k
- Forks
- 11.5k
- Avg merge
- 10m
- Merged PRs (30d)
- 1
Description
Currently, there is no clean solution to get extension from X509 certificate or OCSP response. The only way is to call OBJ_create() to add OID into openssl to get a NID, then get extension by NID.
Such solution is infeasible if OpenSSL is used on multiple threads because OBJ_create() is not expected to be used on multiple thread. In addition, even if single thread is used, it will make memory allocated by OBJ_create() cannot be freed until OBJ_cleanup() is called, which is expected to be called in the end of application running. If there are lots of extension retrievals based on OID, the memory usage will keep increasing.
A new API to get extension by OID is really needed.
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 reviewing the existing X509 certificate and OCSP response extension lookup entry points, along with OBJ_create(), to understand how OIDs and NIDs are currently handled. The work is done when a public OID-based lookup API addresses the threading and memory-lifetime concerns described without requiring OBJ_create().
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cryptography
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100