[ech] order of extensions/ssltraceref.txt

[Stephen Farrell]

Hiya,

I'm just rebasing my working branch for ECH, have hit an
issue with the quicapitest and am wondering how best to
handle that.

The issue: quicapitest compares a memory-based trace
against a reference file (ssltraceref.txt) but is failing
in my build as I produce extensions in a different order
so as to be able to handle ECH inner/outer "compression"
which requires "compressed" extensions to be contiguous
in the ClientHello.

The result is that the quicapitest comparison vs. the
reference file fails.

I think the right fix here would be to regenerate the
ssltraceref.txt file but am not sure how to do that.
Can someone advise?

An alternative fix might be to not change the order in
which extensions are encoded when real or GREASE'd ECH
isn't happening, but I think that'd be wrong as it'd likely
be some kind of fingerprint, and probably more brittle once
the QUIC implementation does make use of ECH.

Thanks,
S.

PS: This may well be better handled as a github issue. I
can post the question there later if that's useful.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0xE4D8E9F997A833DD.asc
Type: application/pgp-keys
Size: 1197 bytes
Desc: OpenPGP public key
URL: <https://mta.openssl.org/pipermail/ech/attachments/20230822/20af4455/attachment-0001.asc>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 236 bytes
Desc: OpenPGP digital signature
URL: <https://mta.openssl.org/pipermail/ech/attachments/20230822/20af4455/attachment-0001.sig>