Email Name Constraints
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- rust
- Domain
- cryptography, security
Research direction
Start with RFC 2821 section 4.1.2 for Mailbox parsing and RFC 5280 section 4.2.1.10 for email name constraints, then compare the existing name-constraints handling in webpki. Review the email_address crate as a reference while deciding whether a dependency is appropriate. Done means email SAN constraints are implemented according to the X.509 specification and validated by relevant tests.
Written by the indexing model from the issue text.
Description
Hello I saw that currently name constraints aren't implemented to handle email sans. Was wondering if there'd be any problems if I were to make a PR for this? It seems the main work is just to specify what a valid email is and whether it follows said naming constraints.
For defining a valid email, implementing parsing for "Mailbox": https://datatracker.ietf.org/doc/html/rfc2821#section-4.1.2
Then the name constraints portion referring to emails: https://datatracker.ietf.org/doc/html/rfc5280#section-4.2.1.10
It seems like there's at least one other library implementing email parsing: https://docs.rs/email_address/latest/email_address/index.html, but it seems to encapsulate more than what the x509 RFC specifies, so I imagine it'd be better to just write it from scratch here. Also wasn't sure if there were any rules about introducing dependencies.
- Dominant language
- Rust
- Stars
- 167
- Forks
- 112
- Avg merge
- 4h 28m
- Merged PRs (30d)
- 4
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from rustls/webpki
-
Difficulty 4/5 3-5 days Newbie friendliness 22/100
-
Path building re-parses every intermediate on each budgeted call (unbudgeted CPU cost)Possibly taken @batmnnn claimed this 23 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 72/100
-
Improve error message when denying subject name due to wildcard in public suffixMay be free again @ctz claimed this 79 days ago, and no pull request is open. Open
-
Consider all candidate CRLsMay be free again @cpu claimed this 85 days ago, and no pull request is open. Open
-
Add opt-in support for ignoring URI name constraintsPossibly taken @djc claimed this 135 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Similar issues
-
app
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
bug bug jury peripheral:i2s
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
esp-rs/esp-hal#6828 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
ライブラリを追加Openpriority middle
Difficulty 1/5 Under an hour Newbie friendliness 62/100
KATO-Hiro/AtCoderClans#13015 ·
Maintainers usually reply within 1 day
-
needs-review
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
UCS-Care-Group/mailcraft#1429 ·
Maintainers usually reply within 1 day