Skip to content
#

quic

Here are 234 public repositories matching this topic...

nibanks
nibanks commented Jul 7, 2021

Describe the feature you'd like supported

We should change the CID after enough idle time so that any possible NAT rebinding would be harder to be tracked by an outside observer. The simplest way to implement this would be in the flush send code path. When first starting a flush, check how much time has elapsed since the last send. If it's greater than X (20? 30?) seconds force a CID update

good first issue feature request Area: Core
yomo

🦖 Serverless Streaming Framework for Low-latency Edge Computing applications, running atop QUIC protocol, as Metaverse infrastructure, engaging 5G technology and Geo-distributed System.

  • Updated Apr 27, 2022
  • Go
WesleyRosenblum
WesleyRosenblum commented Apr 11, 2022

Problem:

#1255 blocks a number of ports associated with reflection attacks and other issues. There are a few vulnerable ports within the RFC 6056 ephemeral port range of 1024–65535 that are not blocked, as theoretically a client may randomly be assigned one of those ports. This is unlikely, as most Linux kernels and other operating systems follow the RFC 6335 suggested range of 49152–65535.

enhancement good first issue

Improve this page

Add a description, image, and links to the quic topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the quic topic, visit your repo's landing page and select "manage topics."

Learn more