feat: Enable static tls config in Webtransport
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.9k
- Forks
- 1.3k
- Avg merge
- 13d 21h
- Merged PRs (30d)
- 1
Description
We have some code to support a valid TLS cert in the webtransport listener, but we disabled it in https://github.com/libp2p/go-libp2p/pull/1927. There's some subtlety around making it secure.
In the mean time we may bake some assumptions that a webtransport multiaddr mostly has a certhash: https://github.com/libp2p/go-libp2p/pull/2227#discussion_r1151324966. When we re-enable static tls config we should revisit that discussion and see if anything needs to be changed
Contributor guide
No contributing guide indexed for this repository
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 by reviewing the WebTransport listener's TLS support and the changes in pull requests 1927 and 2227, especially the certhash discussion. Re-enable static TLS configuration only after clarifying the security assumptions around WebTransport multiaddrs. Done means valid static TLS certificates work securely and the certhash behavior is consistent with the decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100