tree 693379a7483ab5666856d0ccb71093bfb0d0c4a7
parent 9701e84eff26d0110d21f024debbab88d97e9c81
author Nick Harper <nharper@chromium.org> 1590019169 -0700
committer CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> 1590510662 +0000

Modify how QUIC 0-RTT go/no-go decision is made.

The previous implementation was too strict in its byte-for-byte equality
check including Transport Parameters, because the Transport Parameters
contain a field that QUIC requires be different on each connection. This
change still has BoringSSL do a byte-for-byte check, but now it is only
done over the quic_early_data_context. An additional requirement is
imposed that the quic_early_data_context must be set for early data
capable tickets to be issued.

Bug: 295
Change-Id: I5145c10752b41908b6807c3a3c967653b0c13f37
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/41427
Reviewed-by: David Benjamin <davidben@google.com>
Commit-Queue: David Benjamin <davidben@google.com>