ngtcp2: lack of support for key update makes QUIC connections fail #4612
Trying a HTTP/3 request with ngtcp2 from current git master fails. It results in an assert in ngtcp2 due lack of support for the updated way ngtcp2 wants key updates done.
The new secret is derived from the previous secret. I think curl has to store the first secret somewhere in struct.
In ngtcp2_crypto_update_key, the remembered rx_secret and tx_secret are passed to ngtcp2_crypto_update_key as current_rx_secret and current_tx_secret. The function writes new secret and traffic keys and IVs in the provided buffers.
The text was updated successfully, but these errors were encountered: