Better interoperability with x509-parser
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 505
- Forks
- 157
- Avg merge
- 39m
- Merged PRs (30d)
- 1
Description
It should be possible to generate CertificateParams from an X509Certificate directly, instead of having to go through DER decode/encode. Also methods like DistinguishedName::from_name are private while they could presumably be public.
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 by reviewing the CertificateParams and DistinguishedName APIs, including DistinguishedName::from_name, and compare them with the X509Certificate DER decode/encode path. Done means supporting direct CertificateParams creation from an X509Certificate and making the appropriate name-conversion methods public, with tests covering both behaviors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cryptography, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100