Allow CSR parsing to handle custom extensions
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 505
- Forks
- 157
- Avg merge
- 39m
- Merged PRs (30d)
- 1
Description
Hi,
Currently when using a user defined custom_extensions, this causes the CSR parsing to error out with UnsupportedExtension.
Would it be possible to allow CSR parsing of custom extensions, such as by providing a closure to handle unknown extensions?
Contributor guide
No contributing guide indexed for this repository
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 with CertificateSigningRequest::from_der and the custom_extensions field documentation linked in the issue, then trace where UnsupportedExtension is produced. Determine how unknown or custom extensions should be handled, and verify that a CSR containing a user-defined extension parses successfully without losing the extension data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100