Support all signature algorithms
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 505
- Forks
- 157
- Avg merge
- 39m
- Merged PRs (30d)
- 1
Description
See https://tools.ietf.org/id/draft-ietf-tls-tls13-21.html#rfc.section.4.2.3 for a full list of signature algos.
So far missing:
- PKCS_RSA_SHA384 → a5316e18295fc9dd92031b6039cd18c4549601db
- PKCS_RSA_SHA512 → f9fe8c596b712796a3e8a0ee19907e4d6f5dfe36
- PKCS_RSA_PSS_SHA256
- PKCS_RSA_PSS_SHA384
- PKCS_RSA_PSS_SHA512
- PKCS_ECDSA_P521_SHA512 (depends on https://github.com/briansmith/ring/issues/824)
- PKCS_ED448 (depends on https://github.com/briansmith/ring/issues/463)
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 reading the TLS 1.3 signature algorithm reference linked in the issue and checking rcgen's current supported algorithms. Review the dependency blockers in ring issues 824 and 463; done means the remaining feasible algorithms are supported and covered by the project's existing verification approach.
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
- 25/100