Infrastructure for one TLS session across multiple sockets
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C
- Stars
- 50
- Forks
- 36
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 2
Description
In scenarios where a client kernel makes multiple socket connections to the same server on behalf of the same upper layer protocol (eg, NFS with nconnect), we would like amortize the cost of TLS session set-up by utilizing the same session for all of these connections.
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, tests, or entry points are named. Start by mapping the TLS handshake utilities and Linux kTLS socket handling, then determine how a session could be shared across connections for one upper-layer protocol; done means multiple sockets reuse one TLS session without breaking handshake or connection behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux
- Domain
- networking, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100