quic
Here are 234 public repositories matching this topic...
-
Updated
May 2, 2022 - Go
-
Updated
May 2, 2022 - Rust
I believe these are the knobs for data limits:
https://docs.rs/quinn/latest/quinn/struct.TransportConfig.html#method.stream_receive_window
https://docs.rs/quinn/latest/quinn/struct.TransportConfig.html#method.receive_window
Would like to be able to set these per-connection.
Also, would be great to release this: quinn-rs/quinn#1315
I suppose if a client violates
-
Updated
May 1, 2022 - Go
-
Updated
Feb 18, 2022
More details here
violetagg/reactor-netty-workshop#2
-
Updated
May 2, 2022 - Go
-
Updated
Apr 26, 2022 - TypeScript
file echo_client.c, line:121 st_h->read_stdin_ev = event_new(prog_eb(st_h->client_ctx->prog),
STDIN_FILENO, EV_READ, read_stdin, st_h);
-
Updated
Oct 3, 2021 - Dockerfile
-
Updated
Apr 27, 2022 - Go
-
Updated
Apr 29, 2022 - C
-
Updated
Apr 29, 2022 - C++
-
Updated
Apr 29, 2022 - Vue
-
Updated
Jun 28, 2021 - Python
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.
Improve this page
Add a description, image, and links to the quic topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the quic topic, visit your repo's landing page and select "manage topics."
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