PQ Crypta Logo

Server negotiates only classical X25519 against a hybrid offer

Either outcome is conformant and the report says which was taken. A client that proceeds has chosen availability: the connection is classically secure and it accepted that. A client that refuses has chosen a post-quantum floor, which is a policy some deployments now require and no RFC yet mandates. No grade is attached, because attaching one would invent a requirement. What is worth knowing is that the answer is a deliberate choice rather than an accident, and today most clients cannot express it either way.

PQ CRYPTA PLATFORM

🏠 Main

🧪 Interactive Apps

📰 News

🛡️ PQ Crypta Proxy

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

t-classical-only · RFC 8446 §4.1.1, draft-ietf-tls-hybrid-design §5 · discretionary · layer tls · udp/4512 · MAY

Passing this means: The RFC permits either behaviour; the report says which was chosen.

Anomaly type: transport

How each client answered

ClientVersionVerdictWhat happened
curl ngtcp2/1.11.0 Pass Tolerated it and continued. The specification permits this but does not require it; a client that rejected it would also be conformant.
quinn noq fork Pass Handled it: declined to negotiate when only the classical X25519 was offered, which is a deliberate post-quantum floor. No RFC requires this and none forbids it.
aioquic 1.3.0 Pass Tolerated it and continued. The specification permits this but does not require it; a client that rejected it would also be conformant.
chromium build 1223 Pass Tolerated it and continued. The specification permits this but does not require it; a client that rejected it would also be conformant.
quic-go quic-go v0.61.0 Pass Tolerated it and continued. The specification permits this but does not require it; a client that rejected it would also be conformant.
quiche 0.30.0 Pass Tolerated it and continued. The specification permits this but does not require it; a client that rejected it would also be conformant.
neqo 0.31.1 Pass Tolerated it and continued. The specification permits this but does not require it; a client that rejected it would also be conformant.

What the clause requires

Either outcome is conformant and the report says which was taken. A client that proceeds has chosen availability: the connection is classically secure and it accepted that. A client that refuses has chosen a post-quantum floor, which is a policy some deployments now require and no RFC yet mandates. No grade is attached, because attaching one would invent a requirement. What is worth knowing is that the answer is a deliberate choice rather than an accident, and today most clients cannot express it either way.

Judged against RFC 8446.

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-classical-only")'

What this suite is · The full grid · All clients · All tests · Findings