t-hybrid-large-hello
· RFC 9000 §8.1, §14.1, RFC 9001 §4.4 · resilience · layer tls · udp/4513 · MUST
Passing this means: Recovered rather than giving up.
Anomaly type: transport
How each client answered
| Client | Version | Verdict | What happened |
|---|---|---|---|
| curl | libcurl/8.23.0 ngtcp2/1.25.0 | Pass | Recovered and completed the follow-up request. |
| quinn | noq fork (189b0ed) | Pass | Recovered and completed the follow-up request. |
| aioquic | 1.3.0 (PyPI wheel) | Unsupported | The client offers no key exchange group this port will negotiate, so it was refused before a handshake existed (the cryptographic handshake failed: error 40: peer is incompatible: NoKxGroupsInCommon). That is a capability this client does not have, rather than something the run failed to measure. |
| chromium | build 1248 | Pass | Recovered and completed the follow-up request. |
| quic-go | quic-go v0.61.0 (h1:9So2anK4Tp22) | Pass | Recovered and completed the follow-up request. |
| quiche | 0.30.0 (1c8e976) | Pass | Recovered and completed the follow-up request. |
| neqo | 0.31.1 (cac2b74) | Pass | Recovered and completed the follow-up request. |
| picoquic | 8162550 | Pass | Recovered and completed the follow-up request. |
| ngtcp2 | 3c23148 | Pass | Recovered and completed the follow-up request. |
| lsquic | 4.9.4 (2b30189) | Pass | Recovered and completed the follow-up request. |
| xquic | 2060a44 | Unsupported | The client offers no key exchange group this port will negotiate, so it was refused before a handshake existed (the cryptographic handshake failed: error 40: peer is incompatible: NoKxGroupsInCommon). That is a capability this client does not have, rather than something the run failed to measure. |
| msquic | 2.7.0 (7e6525d) | Unsupported | The client offers no key exchange group this port will negotiate, so it was refused before a handshake existed (the cryptographic handshake failed: error 40: peer is incompatible: NoKxGroupsInCommon). That is a capability this client does not have, rather than something the run failed to measure. |
| quico | 0.7.0 (npm) | Pass | Recovered and completed the follow-up request. |
What the clause requires
Complete the handshake with a ClientHello that does not fit one QUIC Initial packet. An ML-KEM-768 key share is 1,216 bytes, which pushes a ClientHello past the 1,200-byte floor RFC 9000 §14.1 sets for an Initial, so the flight must be spread over more than one packet and every one of them padded to the full size. This is the concrete reason post-quantum TLS deployments fail in the field, and it interacts with the §8.1 anti-amplification limit: the server may not send more than three times what it has received, so a client that under-pads its Initials can stall the handshake without either side doing anything invalid.
Judged against RFC 9000, RFC 9001.
Run this one yourself
Every test is reachable from your own client. Nothing here needs an account.
curl -s https://conformance.pqcrypta.com/catalog.json \
| jq '.tests[] | select(.id == "t-hybrid-large-hello")'