OCSP does not expose extension manipulation functions
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 276
- Forks
- 200
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 7
Description
OCSP responses can have extensions. While rarely used in the past, Certificate Transparency (http://tools.ietf.org/html/rfc6962) is using them to deliver information. Currently the only way to add extensions form ruby is to manually modify the ASN.1. It would be nice there was an easier way.
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
The issue names no files, tests, or entry points. Start by locating OCSP response handling and the Ruby OpenSSL bindings for ASN.1 extensions, then review existing extension APIs. Done means Ruby exposes a simpler way to add or manipulate OCSP extensions without manually editing ASN.1.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, ruby
- Domain
- cryptography, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100