diff options
| author | Sergey Kandaurov <pluknet@nginx.com> | 2020-04-17 12:01:45 +0300 |
|---|---|---|
| committer | Sergey Kandaurov <pluknet@nginx.com> | 2020-04-17 12:01:45 +0300 |
| commit | fa264b46b13d4065341cf5cb578a9b0c6ed2b1d3 (patch) | |
| tree | aedbde8c4078eba68a934148eb388dafe66c8556 /src | |
| parent | 7288ac486271ed598a662a4e5ebc9833d4f6b8db (diff) | |
| download | nginx-fa264b46b13d4065341cf5cb578a9b0c6ed2b1d3.tar.gz nginx-fa264b46b13d4065341cf5cb578a9b0c6ed2b1d3.tar.bz2 | |
Revert "Rejecting new connections with non-zero Initial packet."
chrome-unstable 83.0.4103.7 starts with Initial packet number 1.
I couldn't find a proper explanation besides this text in quic-transport:
An endpoint MAY skip packet numbers when sending
packets to detect this (Optimistic ACK Attack) behavior.
Diffstat (limited to 'src')
| -rw-r--r-- | src/event/ngx_event_quic.c | 6 |
1 files changed, 0 insertions, 6 deletions
diff --git a/src/event/ngx_event_quic.c b/src/event/ngx_event_quic.c index 34a51f71f..4c9a658a9 100644 --- a/src/event/ngx_event_quic.c +++ b/src/event/ngx_event_quic.c @@ -583,12 +583,6 @@ ngx_quic_new_connection(ngx_connection_t *c, ngx_ssl_t *ssl, ngx_quic_tp_t *tp, return NGX_ERROR; } - if (pkt->pn != 0) { - ngx_log_error(NGX_LOG_INFO, c->log, 0, - "invalid initial packet number %L", pkt->pn); - return NGX_ERROR; - } - if (ngx_quic_init_connection(c) != NGX_OK) { return NGX_ERROR; } |