Hybrid (classical crypto + PQ) TLS in CCF
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 876
- Forks
- 260
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 157
Description
For both user-to-node and node-to-node, details TBD. Use of PQ or hybrid certs is still undefined. A minimum acceptance criteria would be to enable hybrid secret exchange to protect from HNDL attacks.
-------
Progress
- [x] User TLS (#8107)
- [ ] N2N (needs replacing custom channels with TLS 1.3 + QUIC)
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 the completed user TLS work in #8107, then investigate the node-to-node path and its custom channels. The remaining work is to replace those channels with TLS 1.3 and QUIC, with hybrid secret exchange protecting against HNDL attacks; certificate details remain undefined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cryptography, distributed-systems, networking, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100