rfc_violation_no_change_after_hrr

Function rfc_violation_no_change_after_hrr 

Source
pub fn rfc_violation_no_change_after_hrr(
    client: AgentName,
) -> Trace<TLSProtocolTypes>
Expand description

When receiving a HelloRetryRequest (ServerHello with magic random value) which should trigger no change in the ClientHello (the HRR only contains a SupportedVersion extension), WolfSSL TLS 1.3 client sends a ClientHello that is identical to its first ClientHello. https://github.com/wolfSSL/wolfssl/issues/9247