Thanks David.
Cheers,
S.
On 17/08/2021 21:15, David Benjamin wrote:
It's because of the rules in RFC8446. If the server doesn't utter an
extension in HelloRetryRequest, the client is not allowed to change the
corresponding ClientHello extension. We found an implementation which
actually enforce
It's because of the rules in RFC8446. If the server doesn't utter an
extension in HelloRetryRequest, the client is not allowed to change the
corresponding ClientHello extension. We found an implementation which
actually enforces this.
https://github.com/tlswg/draft-ietf-tls-esni/issues/358
David
Hiya,
(I'm just getting around to playing with draft-13 ECH and
HRR and have a question...)
In 6.2 talking about GREASEd ECH, the draft says:
If sending a second ClientHello in response to a
HelloRetryRequest, the client copies the entire
"encrypted_client_hello" extension from the fi
