python-trio / python-trio/trustme
Follow CAFB guidelines more closely?
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 608
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
There are a bunch of ways we aren't really following CAFB rules. Not sure how much it matters. But for example:
7.1.2.1 rules for root certificates:
- SHOULD NOT set
path_length - MUST include
keyUsage- MUST be marked critical
- MUST have keyCertSign and cRLSign set
7.1.4.3 CA certificates:
- MUST have a common name, organization name, and country name
7.1.2.3 subscriber certificates:
- MUST have certificatePolicies
- MUST have extKeyUsage
We might have some RFC 5280 fails too, I haven't read it carefully.
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
No files or tests are named. Begin by auditing trustme's certificate generation against the listed CAFB sections and RFC 5280, then define the affected requirements and how each will be verified as complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- security
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100