Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Quant server misbehaves when a ping is sent as the first Initial packet. #83

Open
QUICTester opened this issue Jul 14, 2023 · 1 comment
Labels

Comments

@QUICTester
Copy link

Hi,

During testing commit 511d91c, we discovered that when a Ping frame is sent as the first message, the Quant server misbehaves. The quant server sends another Ping instead of acknowledging the Ping sent by the client. However, when the client acknowledges the server's Ping, the server send close the connection with "got ACK for Initial pkt 0 never sent" error message.

We believe this is because the Quant server does not properly handle the first packet sent by the client if the first packet does not contain a CRYPTO frame that carries Client Hello (quant/lib/src/conn.c:1044 in the latest commit). As stated in RFC 9000, the Initial packet can carry a Ping frame. This means sending a Ping in the first Initial packet is possible.

@larseggert larseggert added the bug label Jul 17, 2023
@larseggert
Copy link
Contributor

Thanks for the report. It's very likely that you identified a bug. Quant isn't under active maintenance anymore, since it was meant as a proof-of-concept to validate the evolving QUIC spec during its standardization. So it's unlikely I'll fix this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants