tlshd should check the ALPN and extended key usage
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C
- Stars
- 50
- Forks
- 36
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 2
Description
RFC 9289 specifies an Application-Layer Protocol Negotiation (ALPN) identifier for RPC-with-TLS, in addition to new extended key usage OIDs for RPC-with-TLS. Either tlshd or the kernel's RPC stack need to deal with these during certificate verification.
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
Start with RFC 9289 and trace certificate verification in tlshd and the kernel RPC stack to determine where ALPN and the new extended key usage OIDs are handled. Done means the appropriate component verifies both requirements during RPC-with-TLS setup, with coverage for the affected verification path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux
- Domain
- networking, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100