QUIC anti-replay is faked and insecure
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 50
- Forks
- 36
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 2
Description
QUIC 0-RTT requires anti-replay protection to be secure. This is currently being faked in tlshd by setting a callback function of tlshd_quic_server_anti_replay_db_add_func(), which always returns 0 (not a replay).
All of the current anti-replay initialisation should be removed until a real anti-replay callback is implemented. It appears to be optional and GnuTLS will disable 0-RTT if gnutls_anti_replay_enable() is not called.
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
Locate tlshd_quic_server_anti_replay_db_add_func() and the surrounding QUIC anti-replay initialization. Check how GnuTLS behaves when gnutls_anti_replay_enable() is not called, then verify that the insecure always-zero callback setup is no longer active and that 0-RTT is disabled until a real callback exists.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100