quic: require address validation when under load
Nobody has claimed this yet.
- #1602 by @fulviodenza — closed without merging
- Dominant language
- Go
- Stars
- 6.9k
- Forks
- 1.3k
- Avg merge
- 13d 21h
- Merged PRs (30d)
- 1
Description
Address validation makes sure that the client actually has the IP address that it claims to have.
By validating the address before sending a lot of data (e.g. the certificate chain) to the client, we avoid being used for reflection attacks. However, this adds one roundtrip to connection setup.
We should come up with some heuristics. An easy method would be counting the number of connection attempts per a fixed duration, and only require address validation if more connections are received.
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 QUIC connection-setup path and its address-validation handling. Examine the proposed connection-attempt rate heuristic and define how load should trigger validation; done means the behavior is implemented and verified against reflection-attack protection and connection setup costs.
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
- Needs clarification
- Newbie friendliness
- 20/100